Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3006170677edd09b7628b7e9f85e0a40e0f543a44b5ddd391c35265bd99b74

Tx prefix hash: 2e44ecdcb243c326c26346e17cb4e61b83c7473b34a9b1be757e7adffb748897
Tx public key: 2b673e81de8944186b923e5da67b4b52312d0fda52fd32047f4f11bf4ebb5e96
Timestamp: 1751894679 Timestamp [UCT]: 2025-07-07 13:24:39 Age [y:d:h:m:s]: 00:132:23:51:00
Block: 1320630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93484 RingCT/type: yes/0
Extra: 012b673e81de8944186b923e5da67b4b52312d0fda52fd32047f4f11bf4ebb5e96021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46a327169dac6d2c61928cb4b71b62200f6ce5d4bba7aa0068e123828fb0a603 0.600000000000 1808329 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": 1320640, "vin": [ { "gen": { "height": 1320630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46a327169dac6d2c61928cb4b71b62200f6ce5d4bba7aa0068e123828fb0a603" } } ], "extra": [ 1, 43, 103, 62, 129, 222, 137, 68, 24, 107, 146, 62, 93, 166, 123, 75, 82, 49, 45, 15, 218, 82, 253, 50, 4, 127, 79, 17, 191, 78, 187, 94, 150, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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