Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed1a495248c0410bd8e28149ddde6e70a58e46e7cd897ddc116569964fd267b0

Tx prefix hash: d686cad70d13f799c9b45e928a21c898c8f468d3081e73c2dd9c9c5a2016d10a
Tx public key: 805ea6e5b56bb89319eadf620b1409c91eb53e00a9e77d28cabb19153a3e3285
Timestamp: 1699909322 Timestamp [UCT]: 2023-11-13 21:02:02 Age [y:d:h:m:s]: 01:361:03:51:36
Block: 890996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517018 RingCT/type: yes/0
Extra: 01805ea6e5b56bb89319eadf620b1409c91eb53e00a9e77d28cabb19153a3e3285021100000002679a8a81000000000000000000

1 output(s) for total of 0.685110113000 dcy

stealth address amount amount idx
00: 97f3b2ef41ad40845ecca2e0e15ae887dcba53fb82bf94a9d695b7de891d93fc 0.685110113000 1347031 of 0

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": 891006, "vin": [ { "gen": { "height": 890996 } } ], "vout": [ { "amount": 685110113, "target": { "key": "97f3b2ef41ad40845ecca2e0e15ae887dcba53fb82bf94a9d695b7de891d93fc" } } ], "extra": [ 1, 128, 94, 166, 229, 181, 107, 184, 147, 25, 234, 223, 98, 11, 20, 9, 201, 30, 181, 62, 0, 169, 231, 125, 40, 202, 187, 25, 21, 58, 62, 50, 133, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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