Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd30fff95aaf7500b083bbecb4e53296dc3d5cf510def391ee8d072625cde004

Tx prefix hash: 62cce9808e05f7f3a4ef2e3fb8bd133de4a7bdb057f8814def70b859c593bb9f
Tx public key: 8d06b808e81cec32dd765a9336c7bf293bd4302e52e137d246b628d22fec05a0
Timestamp: 1725557686 Timestamp [UCT]: 2024-09-05 17:34:46 Age [y:d:h:m:s]: 00:258:08:44:59
Block: 1103636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184540 RingCT/type: yes/0
Extra: 018d06b808e81cec32dd765a9336c7bf293bd4302e52e137d246b628d22fec05a0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9712e8bb7a2dc4975441e4b0b5ffdf92ef8e9ec634897269d6d124623eec7f84 0.600000000000 1580541 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": 1103646, "vin": [ { "gen": { "height": 1103636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9712e8bb7a2dc4975441e4b0b5ffdf92ef8e9ec634897269d6d124623eec7f84" } } ], "extra": [ 1, 141, 6, 184, 8, 232, 28, 236, 50, 221, 118, 90, 147, 54, 199, 191, 41, 59, 212, 48, 46, 82, 225, 55, 210, 70, 182, 40, 210, 47, 236, 5, 160, 2, 17, 0, 0, 0, 2, 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