Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07024e1cb1372c1e70c81d324f8c89b876d7ffef1ef9580a8e1f05019e4b73c0

Tx prefix hash: 0d1651faf66d40dcead44ebd754ec3adefcafd81730f6e0179ced97b297cc677
Tx public key: 8be45c314e6f4c98884ba390e3a84a5ed1a0ac5a26dcbccec9a0901ad574b529
Timestamp: 1765910987 Timestamp [UCT]: 2025-12-16 18:49:47 Age [y:d:h:m:s]: 00:006:23:45:01
Block: 1435035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5005 RingCT/type: yes/0
Extra: 018be45c314e6f4c98884ba390e3a84a5ed1a0ac5a26dcbccec9a0901ad574b529021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe639fc0345346792191d860b33eb2b1657f71edeb0f1f2590b01ed10254720 0.600000000000 1923832 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": 1435045, "vin": [ { "gen": { "height": 1435035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe639fc0345346792191d860b33eb2b1657f71edeb0f1f2590b01ed10254720" } } ], "extra": [ 1, 139, 228, 92, 49, 78, 111, 76, 152, 136, 75, 163, 144, 227, 168, 74, 94, 209, 160, 172, 90, 38, 220, 188, 206, 201, 160, 144, 26, 213, 116, 181, 41, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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