Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54cb2307f30225dc4c840c431223f5374f5b2e6ffb34690ff709543ec037c8c8

Tx prefix hash: 7e7a87e5c858a22f1ed46041ddfc3d235769cb50564818d5689d76f3d095889a
Tx public key: 42c37b9feaec50d690d840bb880ad1a5fd81f98386d09518c6ceb3341aba3a0b
Timestamp: 1674608380 Timestamp [UCT]: 2023-01-25 00:59:40 Age [y:d:h:m:s]: 01:253:23:37:49
Block: 682119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442494 RingCT/type: yes/0
Extra: 0142c37b9feaec50d690d840bb880ad1a5fd81f98386d09518c6ceb3341aba3a0b021100000001e7ace25d000000000000000000

1 output(s) for total of 3.371759047000 dcy

stealth address amount amount idx
00: 0995b8d4e0b67f09c8f24c4ff6e0e7c4919506e2a80a9bfe59a19ca72c4d5008 3.371759047000 1124234 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": 682129, "vin": [ { "gen": { "height": 682119 } } ], "vout": [ { "amount": 3371759047, "target": { "key": "0995b8d4e0b67f09c8f24c4ff6e0e7c4919506e2a80a9bfe59a19ca72c4d5008" } } ], "extra": [ 1, 66, 195, 123, 159, 234, 236, 80, 214, 144, 216, 64, 187, 136, 10, 209, 165, 253, 129, 249, 131, 134, 208, 149, 24, 198, 206, 179, 52, 26, 186, 58, 11, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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