Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01675317764b241ec746b0397d4b060695c3496a062be49ceab070f59b0a192

Tx prefix hash: a930005f0febf73540fc6ed3c30252e099f2cbeb705fdc521f1a92ce5dd54669
Tx public key: 3be9a7eeb2b4c64632ee5f6f7f423ba67aaa640e4852f30206c082ea9f5281fc
Timestamp: 1724040209 Timestamp [UCT]: 2024-08-19 04:03:29 Age [y:d:h:m:s]: 00:225:23:12:26
Block: 1091059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161347 RingCT/type: yes/0
Extra: 013be9a7eeb2b4c64632ee5f6f7f423ba67aaa640e4852f30206c082ea9f5281fc02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1be165032b2dbd85127facb4b2991b26a2d64a8f0fdef97a1ca95ba4738364 0.600000000000 1565684 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": 1091069, "vin": [ { "gen": { "height": 1091059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1be165032b2dbd85127facb4b2991b26a2d64a8f0fdef97a1ca95ba4738364" } } ], "extra": [ 1, 59, 233, 167, 238, 178, 180, 198, 70, 50, 238, 95, 111, 127, 66, 59, 166, 122, 170, 100, 14, 72, 82, 243, 2, 6, 192, 130, 234, 159, 82, 129, 252, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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