Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e68715c3de20207f9effa3a4a0751b054c295ec5a026912c21cb1b52e2d6022

Tx prefix hash: e2b48d6f4c556316ce2b61238e288626becb1dfe7b2340440e4f2088d734c434
Tx public key: 8d464417e3846c1d6e66aa986655a4443f905b33efefcface3b22cabc2e22d8c
Timestamp: 1703895423 Timestamp [UCT]: 2023-12-30 00:17:03 Age [y:d:h:m:s]: 01:167:10:18:43
Block: 924033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380750 RingCT/type: yes/0
Extra: 018d464417e3846c1d6e66aa986655a4443f905b33efefcface3b22cabc2e22d8c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1953c632b73e748097b2e88f416e30b35827c19958646f0d787b6df1df1f145c 0.600000000000 1381775 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": 924043, "vin": [ { "gen": { "height": 924033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1953c632b73e748097b2e88f416e30b35827c19958646f0d787b6df1df1f145c" } } ], "extra": [ 1, 141, 70, 68, 23, 227, 132, 108, 29, 110, 102, 170, 152, 102, 85, 164, 68, 63, 144, 91, 51, 239, 239, 207, 172, 227, 178, 44, 171, 194, 226, 45, 140, 2, 17, 0, 0, 0, 2, 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