Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac6018483e8b410010748978875d8c0e4e29eb5aff1ff0899e39ecd8b333cde9

Tx prefix hash: 7d24ada4f295277ea8104ac67de6bfc991cc17493b3844048b4ba3a28c548ed2
Tx public key: b0f2cddd737269f326262caf30cd98c7fbb769d8d2a1a2a008801e9eca1d07fe
Timestamp: 1751546108 Timestamp [UCT]: 2025-07-03 12:35:08 Age [y:d:h:m:s]: 00:140:23:28:01
Block: 1317939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98995 RingCT/type: yes/0
Extra: 01b0f2cddd737269f326262caf30cd98c7fbb769d8d2a1a2a008801e9eca1d07fe02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4ddef908f84c421a79ba328244cb7ec18ae7ed1db455acfd7e7e9ae34f61f4 0.600000000000 1805610 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": 1317949, "vin": [ { "gen": { "height": 1317939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4ddef908f84c421a79ba328244cb7ec18ae7ed1db455acfd7e7e9ae34f61f4" } } ], "extra": [ 1, 176, 242, 205, 221, 115, 114, 105, 243, 38, 38, 44, 175, 48, 205, 152, 199, 251, 183, 105, 216, 210, 161, 162, 160, 8, 128, 30, 158, 202, 29, 7, 254, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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