Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 157ebe7e4098a0fd922252ec3f11dc676c19a7c7f56bdac0413c22cdf7c25d9f

Tx prefix hash: 20746b6c6ad2ca6759db3d9ad8017d08db682b84080342d2bee6d8a4a1b2b494
Tx public key: 22f04540332f25e2fc794be57edb6255ee5fb6bad776b29ccaa44af94a52964d
Timestamp: 1745985081 Timestamp [UCT]: 2025-04-30 03:51:21 Age [y:d:h:m:s]: 00:247:10:10:56
Block: 1272471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174611 RingCT/type: yes/0
Extra: 0122f04540332f25e2fc794be57edb6255ee5fb6bad776b29ccaa44af94a52964d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10a292fae8b09ea8dc00b5c194fe9c968f17f11a8a2dc3cdf6fc7ef604d289d5 0.600000000000 1759746 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": 1272481, "vin": [ { "gen": { "height": 1272471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10a292fae8b09ea8dc00b5c194fe9c968f17f11a8a2dc3cdf6fc7ef604d289d5" } } ], "extra": [ 1, 34, 240, 69, 64, 51, 47, 37, 226, 252, 121, 75, 229, 126, 219, 98, 85, 238, 95, 182, 186, 215, 118, 178, 156, 202, 164, 74, 249, 74, 82, 150, 77, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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