Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 183e3d134bd392596f783c7c8404ad95c88cec307f902b96403a9089382454c4

Tx prefix hash: d1dd7853fe2bcb14e90d829e9c03d7fd7733dcf21af9722cb96932fcc73cc38f
Tx public key: ab2bdba6ed3ae30bfcfb04a3d6903a58e52269bd6032d3725e13b92f591dd156
Timestamp: 1721913846 Timestamp [UCT]: 2024-07-25 13:24:06 Age [y:d:h:m:s]: 00:312:18:08:32
Block: 1073424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223486 RingCT/type: yes/0
Extra: 01ab2bdba6ed3ae30bfcfb04a3d6903a58e52269bd6032d3725e13b92f591dd156021100000019e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d1a35d5eb5eb473e95c01f14a37e94303e1d9a2897e84acfb265c9db8c8189 0.600000000000 1545925 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": 1073434, "vin": [ { "gen": { "height": 1073424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d1a35d5eb5eb473e95c01f14a37e94303e1d9a2897e84acfb265c9db8c8189" } } ], "extra": [ 1, 171, 43, 219, 166, 237, 58, 227, 11, 252, 251, 4, 163, 214, 144, 58, 88, 229, 34, 105, 189, 96, 50, 211, 114, 94, 19, 185, 47, 89, 29, 209, 86, 2, 17, 0, 0, 0, 25, 233, 20, 221, 21, 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