Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85bfb70f6d32af0566e772adc4b68b5918905ce85925692acb8e4dd3bf56308e

Tx prefix hash: b740961bd6500e185c0253eeb85d931aa99fa10f37f982c14ae35c15340dc19a
Tx public key: 2d6bcaf1f03641b95abe68dfdd72c6e3d82f44d15c4ef9082f5509e41df873e0
Timestamp: 1764739289 Timestamp [UCT]: 2025-12-03 05:21:29 Age [y:d:h:m:s]: 00:000:21:26:02
Block: 1425332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640 RingCT/type: yes/0
Extra: 012d6bcaf1f03641b95abe68dfdd72c6e3d82f44d15c4ef9082f5509e41df873e0021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f0ff3c622223be5c485e2abb0896e215d341e0c35b2df9e361809a22606962 0.600000000000 1913965 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": 1425342, "vin": [ { "gen": { "height": 1425332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f0ff3c622223be5c485e2abb0896e215d341e0c35b2df9e361809a22606962" } } ], "extra": [ 1, 45, 107, 202, 241, 240, 54, 65, 185, 90, 190, 104, 223, 221, 114, 198, 227, 216, 47, 68, 209, 92, 78, 249, 8, 47, 85, 9, 228, 29, 248, 115, 224, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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