Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 825363a20c3b8a84863ee150cad2ab545c384c98174ba27e1377ba3a7b22d35b

Tx prefix hash: d8db64d67df3aab4a4a92a2e2299318f00a76fcf72333bdcaa261a1d2dfbd987
Tx public key: 7c8f7ac4de962a205fa13de1001521e5fb1b49b6625bf5f89cea5065fc90e1fd
Timestamp: 1749971475 Timestamp [UCT]: 2025-06-15 07:11:15 Age [y:d:h:m:s]: 00:156:19:44:48
Block: 1305371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109866 RingCT/type: yes/0
Extra: 017c8f7ac4de962a205fa13de1001521e5fb1b49b6625bf5f89cea5065fc90e1fd0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7c0b933e7772ed3e5b217ba71d19ce13c69876f9a0c63fdd257711b8257e0f5 0.600000000000 1792970 of 15

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": 1305381, "vin": [ { "gen": { "height": 1305371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7c0b933e7772ed3e5b217ba71d19ce13c69876f9a0c63fdd257711b8257e0f5" } } ], "extra": [ 1, 124, 143, 122, 196, 222, 150, 42, 32, 95, 161, 61, 225, 0, 21, 33, 229, 251, 27, 73, 182, 98, 91, 245, 248, 156, 234, 80, 101, 252, 144, 225, 253, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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