Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7108ff36cd978db25ce83bfb13db0efa896991c930e40d6c04cfea0f5d4a8f62

Tx prefix hash: f8ad3a42df6cb98145dc40d6ef0a003b6f2def8e349db7a22b03e1cb9e9bfe1e
Tx public key: e365393088f963511bcc12097ee3fe92c39738fc149b501f91808449a0e856f7
Timestamp: 1714240150 Timestamp [UCT]: 2024-04-27 17:49:10 Age [y:d:h:m:s]: 01:186:07:34:29
Block: 1009802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391804 RingCT/type: yes/0
Extra: 01e365393088f963511bcc12097ee3fe92c39738fc149b501f91808449a0e856f70211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2cf3eda9b598b92a5ddeaf545edf6ea77ec0269478f46378e6e910bbdf3fd9f 0.600000000000 1471574 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": 1009812, "vin": [ { "gen": { "height": 1009802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2cf3eda9b598b92a5ddeaf545edf6ea77ec0269478f46378e6e910bbdf3fd9f" } } ], "extra": [ 1, 227, 101, 57, 48, 136, 249, 99, 81, 27, 204, 18, 9, 126, 227, 254, 146, 195, 151, 56, 252, 20, 155, 80, 31, 145, 128, 132, 73, 160, 232, 86, 247, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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