Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1d9b3d2ec35bcae8eb29569b2ba72b300ca378635cc5d96c1fca08bb14383626

Tx prefix hash: 20b405363f62b73c847d0ce69bf5b13bb2661828e0aa142663d0b2bf1d61f53b
Tx public key: cc50000351195714e2f7f1aa8c298919c8ffa3530773a039a2a3ab2f90c5684b
Timestamp: 1675607734 Timestamp [UCT]: 2023-02-05 14:35:34 Age [y:d:h:m:s]: 02:301:23:42:34
Block: 690406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735216 RingCT/type: yes/0
Extra: 01cc50000351195714e2f7f1aa8c298919c8ffa3530773a039a2a3ab2f90c5684b021100000004835e4d22000000000000000000

1 output(s) for total of 3.165178800000 dcy

stealth address amount amount idx
00: 1da2644d0b23633fdcf617ce8c354f672902415a4115b76c2a25a53b1d8fdb8a 3.165178800000 1133134 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 690416, "vin": [ { "gen": { "height": 690406 } } ], "vout": [ { "amount": 3165178800, "target": { "key": "1da2644d0b23633fdcf617ce8c354f672902415a4115b76c2a25a53b1d8fdb8a" } } ], "extra": [ 1, 204, 80, 0, 3, 81, 25, 87, 20, 226, 247, 241, 170, 140, 41, 137, 25, 200, 255, 163, 83, 7, 115, 160, 57, 162, 163, 171, 47, 144, 197, 104, 75, 2, 17, 0, 0, 0, 4, 131, 94, 77, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8