Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f302b7e0986ea3c5389dcbe3c9caa437ff122fadb7f7646643e71e0389d36e7

Tx prefix hash: 95286656d165f20ceb0661a0f814cb0912aec537e0e1f1a66f210b105517a64e
Tx public key: e760b24c31efb2e5e61438ad1ccf1f79b2da35db945b68acc7a51df48048142a
Timestamp: 1708205862 Timestamp [UCT]: 2024-02-17 21:37:42 Age [y:d:h:m:s]: 01:114:05:46:45
Block: 959771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342726 RingCT/type: yes/0
Extra: 01e760b24c31efb2e5e61438ad1ccf1f79b2da35db945b68acc7a51df48048142a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3595eae8addbf3d13209a545670079467422f7e648fee7d17117ff28bb1be9c9 0.600000000000 1419324 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": 959781, "vin": [ { "gen": { "height": 959771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3595eae8addbf3d13209a545670079467422f7e648fee7d17117ff28bb1be9c9" } } ], "extra": [ 1, 231, 96, 178, 76, 49, 239, 178, 229, 230, 20, 56, 173, 28, 207, 31, 121, 178, 218, 53, 219, 148, 91, 104, 172, 199, 165, 29, 244, 128, 72, 20, 42, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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