Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4bc38760729f1739aae5aef718386fcb04c7a6a0c37d81d972bcdde01abdc95

Tx prefix hash: 31311f7c656c78a7d682a22281d33ae3c73fc6bba864405a6e82f837bc975bcb
Tx public key: 770dc20a84958a1e2a07024f80e956fc199a47c665f4c873e18f1057cacffdc8
Timestamp: 1715100827 Timestamp [UCT]: 2024-05-07 16:53:47 Age [y:d:h:m:s]: 00:335:05:55:03
Block: 1016941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239625 RingCT/type: yes/0
Extra: 01770dc20a84958a1e2a07024f80e956fc199a47c665f4c873e18f1057cacffdc80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39c54c6620320cb22836fbbf02005f5df82e47a68536a1e511beda98289b4a4b 0.600000000000 1480674 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": 1016951, "vin": [ { "gen": { "height": 1016941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39c54c6620320cb22836fbbf02005f5df82e47a68536a1e511beda98289b4a4b" } } ], "extra": [ 1, 119, 13, 194, 10, 132, 149, 138, 30, 42, 7, 2, 79, 128, 233, 86, 252, 25, 154, 71, 198, 101, 244, 200, 115, 225, 143, 16, 87, 202, 207, 253, 200, 2, 17, 0, 0, 0, 4, 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