Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 770b4de375fcd754512a3c4f35f6d931b9e8052605e3fb303d9e371a8bffd9d2

Tx prefix hash: 1364b45131a1131cc833958fb94d1c2a563b4307a250d0f6815e210de8601334
Tx public key: 8b31e035f296ed507df9589e984dcf3476e1fff465bdc3c959fd474781237346
Timestamp: 1744651665 Timestamp [UCT]: 2025-04-14 17:27:45 Age [y:d:h:m:s]: 00:269:01:29:00
Block: 1261427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190092 RingCT/type: yes/0
Extra: 018b31e035f296ed507df9589e984dcf3476e1fff465bdc3c959fd474781237346021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13dfbe4a63df5ebe32d2fc218c8ba28905b929bdeb10d02edff80ae4a3e0cb6d 0.600000000000 1748596 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": 1261437, "vin": [ { "gen": { "height": 1261427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13dfbe4a63df5ebe32d2fc218c8ba28905b929bdeb10d02edff80ae4a3e0cb6d" } } ], "extra": [ 1, 139, 49, 224, 53, 242, 150, 237, 80, 125, 249, 88, 158, 152, 77, 207, 52, 118, 225, 255, 244, 101, 189, 195, 201, 89, 253, 71, 71, 129, 35, 115, 70, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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