Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13b1e95ec02e2e5ace7f2f4dcce357852c57f08956e94a5bdbdd3d81038b023

Tx prefix hash: e6ec62179ccae3e890fa648ce2bcb515fc3d1932afcf007bdcfd19a4b63a5d62
Tx public key: be58f094718c876c6bad30ef15eedf1290d54d43a0bc629c5c5b59de853d257a
Timestamp: 1712244336 Timestamp [UCT]: 2024-04-04 15:25:36 Age [y:d:h:m:s]: 01:033:00:10:42
Block: 993228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284602 RingCT/type: yes/0
Extra: 01be58f094718c876c6bad30ef15eedf1290d54d43a0bc629c5c5b59de853d257a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78d43dadd312fe411d6927f9a41cf36aced8933ac706c3209e1f5267c9636428 0.600000000000 1453614 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": 993238, "vin": [ { "gen": { "height": 993228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d43dadd312fe411d6927f9a41cf36aced8933ac706c3209e1f5267c9636428" } } ], "extra": [ 1, 190, 88, 240, 148, 113, 140, 135, 108, 107, 173, 48, 239, 21, 238, 223, 18, 144, 213, 77, 67, 160, 188, 98, 156, 92, 91, 89, 222, 133, 61, 37, 122, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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