Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fbc50928c551669680c40e33b6653d756316fb974e80c0274cb39efc0a3156f

Tx prefix hash: 459c9a5cdd337468307fec7e1c683a5356b27f3a1d5ce0eb91cf817b2f00ac8b
Tx public key: e8e7f9aac67e2603a301b87822338c917ef309e680f2391fefdd91e04b1033df
Timestamp: 1748407516 Timestamp [UCT]: 2025-05-28 04:45:16 Age [y:d:h:m:s]: 00:170:04:05:14
Block: 1292530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119310 RingCT/type: yes/0
Extra: 01e8e7f9aac67e2603a301b87822338c917ef309e680f2391fefdd91e04b1033df02110000000786ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d294e8c8e933c5f5a567bb99191697e8e582d9ad9d4e11a0906c139ef2313006 0.600000000000 1780001 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": 1292540, "vin": [ { "gen": { "height": 1292530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d294e8c8e933c5f5a567bb99191697e8e582d9ad9d4e11a0906c139ef2313006" } } ], "extra": [ 1, 232, 231, 249, 170, 198, 126, 38, 3, 163, 1, 184, 120, 34, 51, 140, 145, 126, 243, 9, 230, 128, 242, 57, 31, 239, 221, 145, 224, 75, 16, 51, 223, 2, 17, 0, 0, 0, 7, 134, 174, 47, 13, 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