Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29bf82454e4fd2ff826b139b6066af3b7fbad29cc1bfe3e93992c6a46a6ab57f

Tx prefix hash: f9f4fe3317048bcfad1ffa5fc46dbae4c6c8bc3df1beb18cde45b671de40b79a
Tx public key: a77971f8cd745a2fd606d4dd1286edb6ddfa0d81068be1f134b9ee19b3dcc4d1
Timestamp: 1726346911 Timestamp [UCT]: 2024-09-14 20:48:31 Age [y:d:h:m:s]: 00:201:18:05:20
Block: 1110170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144031 RingCT/type: yes/0
Extra: 01a77971f8cd745a2fd606d4dd1286edb6ddfa0d81068be1f134b9ee19b3dcc4d102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16bd3191ea7769176375da5334f99f683213a2afdbb29fb32356d13413c7f006 0.600000000000 1588683 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": 1110180, "vin": [ { "gen": { "height": 1110170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16bd3191ea7769176375da5334f99f683213a2afdbb29fb32356d13413c7f006" } } ], "extra": [ 1, 167, 121, 113, 248, 205, 116, 90, 47, 214, 6, 212, 221, 18, 134, 237, 182, 221, 250, 13, 129, 6, 139, 225, 241, 52, 185, 238, 25, 179, 220, 196, 209, 2, 17, 0, 0, 0, 1, 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