Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fcf4ee415922fb15b109ec8b8c839e5f860660f790cfb240f4eb5104c09469d

Tx prefix hash: 5a01d12e13e66cb95a7588b8c244d2d7dc5a26bd878d319b266f87a522af9f4b
Tx public key: 7e243b8013015f74a8297b2f56480da32c23a330069080ba283379eff576d36b
Timestamp: 1665700603 Timestamp [UCT]: 2022-10-13 22:36:43 Age [y:d:h:m:s]: 03:041:18:58:57
Block: 608440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 810101 RingCT/type: yes/0
Extra: 017e243b8013015f74a8297b2f56480da32c23a330069080ba283379eff576d36b0211000000025029cbac000000000000000000

1 output(s) for total of 5.915422270000 dcy

stealth address amount amount idx
00: c830468f2ca7626f444ca6f5c881842e6e65cf2c64dc61cd59d2f5bbd47f82df 5.915422270000 1045138 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": 608450, "vin": [ { "gen": { "height": 608440 } } ], "vout": [ { "amount": 5915422270, "target": { "key": "c830468f2ca7626f444ca6f5c881842e6e65cf2c64dc61cd59d2f5bbd47f82df" } } ], "extra": [ 1, 126, 36, 59, 128, 19, 1, 95, 116, 168, 41, 123, 47, 86, 72, 13, 163, 44, 35, 163, 48, 6, 144, 128, 186, 40, 51, 121, 239, 245, 118, 211, 107, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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