Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c3356ad9568f3c298b958ef36f09f0f37f07239d26b94396f5df31649ab2dcd

Tx prefix hash: e32ca22c63168407c2e8d76a264cd7a8b72c3bc31e0399e3d95a1b52b5e1dcb8
Tx public key: aab6015406f089dd107c87bc2e4a0732f5f77518a74641c9235e8e920d23fc6d
Timestamp: 1729909435 Timestamp [UCT]: 2024-10-26 02:23:55 Age [y:d:h:m:s]: 00:235:16:06:33
Block: 1139677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168150 RingCT/type: yes/0
Extra: 01aab6015406f089dd107c87bc2e4a0732f5f77518a74641c9235e8e920d23fc6d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54712e3312e20c959caee2441060bcd4c5c7a2062a372069ef61673ccab62ad5 0.600000000000 1623464 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": 1139687, "vin": [ { "gen": { "height": 1139677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54712e3312e20c959caee2441060bcd4c5c7a2062a372069ef61673ccab62ad5" } } ], "extra": [ 1, 170, 182, 1, 84, 6, 240, 137, 221, 16, 124, 135, 188, 46, 74, 7, 50, 245, 247, 117, 24, 167, 70, 65, 201, 35, 94, 142, 146, 13, 35, 252, 109, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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