Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ef85f1564900ec3cc925989785e80354751e45acb316b56f97a18ed8e7f952f

Tx prefix hash: f660be6741f7e92e8b3e10cacf30f9e31b15bc06f7fb5854b910ba18a87f7c29
Tx public key: 36fd32b990b5e835c7b8a06df034a051cfe8c250d03a6dfcf60cadd20d4cc1c6
Timestamp: 1746466710 Timestamp [UCT]: 2025-05-05 17:38:30 Age [y:d:h:m:s]: 00:272:20:34:23
Block: 1276462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192644 RingCT/type: yes/0
Extra: 0136fd32b990b5e835c7b8a06df034a051cfe8c250d03a6dfcf60cadd20d4cc1c60211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c244dfe80d788fb223a0712aa125582a45df003c5df6a2109bc03c5e17ab1fb 0.600000000000 1763805 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": 1276472, "vin": [ { "gen": { "height": 1276462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c244dfe80d788fb223a0712aa125582a45df003c5df6a2109bc03c5e17ab1fb" } } ], "extra": [ 1, 54, 253, 50, 185, 144, 181, 232, 53, 199, 184, 160, 109, 240, 52, 160, 81, 207, 232, 194, 80, 208, 58, 109, 252, 246, 12, 173, 210, 13, 76, 193, 198, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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