Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4555570db48e2ecd88b91bd08b76e6aa1a1ed92b92e39154210b0e9d128e52

Tx prefix hash: ad399df32127509420cba947650790d0fed2f6566a15e10a631006ee7dc68d55
Tx public key: 27a01de5045c5f0adce39c82b87a64f812deec12d658c85b9af1a5f1e733d195
Timestamp: 1703400171 Timestamp [UCT]: 2023-12-24 06:42:51 Age [y:d:h:m:s]: 01:326:10:25:52
Block: 919932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492149 RingCT/type: yes/0
Extra: 0127a01de5045c5f0adce39c82b87a64f812deec12d658c85b9af1a5f1e733d19502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbdbb988e40080fb7a9727ac10efc54fc29a3ad946debba7df88e204b9031e3 0.600000000000 1377610 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": 919942, "vin": [ { "gen": { "height": 919932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbdbb988e40080fb7a9727ac10efc54fc29a3ad946debba7df88e204b9031e3" } } ], "extra": [ 1, 39, 160, 29, 229, 4, 92, 95, 10, 220, 227, 156, 130, 184, 122, 100, 248, 18, 222, 236, 18, 214, 88, 200, 91, 154, 241, 165, 241, 231, 51, 209, 149, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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