Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1e249c56192761ea7c46594537199d11137cb306151bde0830fc656a12adebd

Tx prefix hash: d924cc2ba72a75d8c1107dc9666af87cb8d2c316965c271c4f2889419431e8c3
Tx public key: 1b909acd5fa405c5f6711e80ee03b846ed40f662c00d510ea791db0a3cc5b7b0
Timestamp: 1746377216 Timestamp [UCT]: 2025-05-04 16:46:56 Age [y:d:h:m:s]: 00:194:08:09:47
Block: 1275708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136609 RingCT/type: yes/0
Extra: 011b909acd5fa405c5f6711e80ee03b846ed40f662c00d510ea791db0a3cc5b7b00211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a54935936aff6b9a2e449bcb37c2986a3fdf49ec88feb1febec4bc6316075798 0.600000000000 1763023 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": 1275718, "vin": [ { "gen": { "height": 1275708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54935936aff6b9a2e449bcb37c2986a3fdf49ec88feb1febec4bc6316075798" } } ], "extra": [ 1, 27, 144, 154, 205, 95, 164, 5, 197, 246, 113, 30, 128, 238, 3, 184, 70, 237, 64, 246, 98, 192, 13, 81, 14, 167, 145, 219, 10, 60, 197, 183, 176, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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