Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c48fdc279167856ff64b6cce9e09e460f6d3cc5da6318e7567edf239fb4de1

Tx prefix hash: ae3df494f22dbbe463ee1d111e07a81e6c029ec5e6b3ecb59090b06e3c85c113
Tx public key: 3276ca90754705d6e8c3c8ffbf19f4605a3526729b4b9dcf40f0cae608e1f1cd
Timestamp: 1734849663 Timestamp [UCT]: 2024-12-22 06:41:03 Age [y:d:h:m:s]: 00:005:07:54:14
Block: 1180574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3784 RingCT/type: yes/0
Extra: 013276ca90754705d6e8c3c8ffbf19f4605a3526729b4b9dcf40f0cae608e1f1cd0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3610cf0b6d75177802ed4d68fe5dd202b714324dd985bee5ff365007236cd1cf 0.600000000000 1666987 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": 1180584, "vin": [ { "gen": { "height": 1180574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3610cf0b6d75177802ed4d68fe5dd202b714324dd985bee5ff365007236cd1cf" } } ], "extra": [ 1, 50, 118, 202, 144, 117, 71, 5, 214, 232, 195, 200, 255, 191, 25, 244, 96, 90, 53, 38, 114, 155, 75, 157, 207, 64, 240, 202, 230, 8, 225, 241, 205, 2, 17, 0, 0, 0, 7, 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