Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2edbb55a7322139ebb5ee0d080d3a9a808dac24324f7d4ac4299e40bad2d9a4f

Tx prefix hash: 2ed59760e0aef62f8137aa6e74f961250d1cfd4ebe70f24a4705679c0a768023
Tx public key: 3321196ec4ce67d29be6854a6ff7335a3ef8e696d4594feb8fa437c4921f6a68
Timestamp: 1731612096 Timestamp [UCT]: 2024-11-14 19:21:36 Age [y:d:h:m:s]: 00:175:18:29:57
Block: 1153743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125451 RingCT/type: yes/0
Extra: 013321196ec4ce67d29be6854a6ff7335a3ef8e696d4594feb8fa437c4921f6a6802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 268eef3bd6a3b82ab891466c6cbc5062eea8a1ddb200cbd9d7c2ba9e9b850fba 0.600000000000 1639354 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": 1153753, "vin": [ { "gen": { "height": 1153743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "268eef3bd6a3b82ab891466c6cbc5062eea8a1ddb200cbd9d7c2ba9e9b850fba" } } ], "extra": [ 1, 51, 33, 25, 110, 196, 206, 103, 210, 155, 230, 133, 74, 111, 247, 51, 90, 62, 248, 230, 150, 212, 89, 79, 235, 143, 164, 55, 196, 146, 31, 106, 104, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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