Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67295e3de57157f7e069787344e0e440739e02927cad001e63b5661bcf2157be

Tx prefix hash: 56b5aa4b11e0ff0411a00fbe210626867e785f2591c9d3c2870c7b865fd62f47
Tx public key: 2cee0b41ad265b4a0c0b50409f6779ba149657a075e5a406ebce6961ebed40e0
Timestamp: 1696618041 Timestamp [UCT]: 2023-10-06 18:47:21 Age [y:d:h:m:s]: 01:184:15:39:25
Block: 863908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393007 RingCT/type: yes/0
Extra: 012cee0b41ad265b4a0c0b50409f6779ba149657a075e5a406ebce6961ebed40e0021100000008faf35c9c000000000000000000

1 output(s) for total of 0.842391948000 dcy

stealth address amount amount idx
00: 7f322e7780e74351527a6c38f33aafb3943d434e52bf544bd57a674d0d9d25e6 0.842391948000 1318404 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": 863918, "vin": [ { "gen": { "height": 863908 } } ], "vout": [ { "amount": 842391948, "target": { "key": "7f322e7780e74351527a6c38f33aafb3943d434e52bf544bd57a674d0d9d25e6" } } ], "extra": [ 1, 44, 238, 11, 65, 173, 38, 91, 74, 12, 11, 80, 64, 159, 103, 121, 186, 20, 150, 87, 160, 117, 229, 164, 6, 235, 206, 105, 97, 235, 237, 64, 224, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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