Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97719e906ce7bcdcd7bfe12e4236f9635dfcd12c7e99941aafc89a51757b0499

Tx prefix hash: 7160a20a5dc4c865905d0687614f307756a31dc0df47feafcb1d18afdfdd16f2
Tx public key: d9a42f46085da1fea2aa84277c18597e69a0e494a5ea8510a09dad4b96328f12
Timestamp: 1706797495 Timestamp [UCT]: 2024-02-01 14:24:55 Age [y:d:h:m:s]: 01:280:19:09:53
Block: 948081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459479 RingCT/type: yes/0
Extra: 01d9a42f46085da1fea2aa84277c18597e69a0e494a5ea8510a09dad4b96328f1202110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10da32dfe89826eeb59260ba3438deeb8ef62e3f46a51617a0235408d6064ea0 0.600000000000 1406453 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": 948091, "vin": [ { "gen": { "height": 948081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10da32dfe89826eeb59260ba3438deeb8ef62e3f46a51617a0235408d6064ea0" } } ], "extra": [ 1, 217, 164, 47, 70, 8, 93, 161, 254, 162, 170, 132, 39, 124, 24, 89, 126, 105, 160, 228, 148, 165, 234, 133, 16, 160, 157, 173, 75, 150, 50, 143, 18, 2, 17, 0, 0, 0, 6, 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