Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2001e5a6b056e1488a90225aa714cc0502d7f6f44ff5b2da7eba28c1b213fa51

Tx prefix hash: eb08c9fdce04f1694771fcf6749c43178c7d2c839f8ad747b69a9cf9dbe9ca1f
Tx public key: ac7857ca065c0f1d5c2eda790c2d9cb69e2c4532e6dbe704562ed418684d5910
Timestamp: 1699750979 Timestamp [UCT]: 2023-11-12 01:02:59 Age [y:d:h:m:s]: 01:361:00:40:30
Block: 889685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516916 RingCT/type: yes/0
Extra: 01ac7857ca065c0f1d5c2eda790c2d9cb69e2c4532e6dbe704562ed418684d591002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.691997089000 dcy

stealth address amount amount idx
00: 5b51f3493ef99d0fb643dd56367809c09510da3b5d10b0c3d6b65b0713363cf6 0.691997089000 1345694 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": 889695, "vin": [ { "gen": { "height": 889685 } } ], "vout": [ { "amount": 691997089, "target": { "key": "5b51f3493ef99d0fb643dd56367809c09510da3b5d10b0c3d6b65b0713363cf6" } } ], "extra": [ 1, 172, 120, 87, 202, 6, 92, 15, 29, 92, 46, 218, 121, 12, 45, 156, 182, 158, 44, 69, 50, 230, 219, 231, 4, 86, 46, 212, 24, 104, 77, 89, 16, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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