Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e6cb7ec18cba7ab1286e54ff9201a3f6f09fc224e7755e442b4208443dfb3f

Tx prefix hash: 976166efdc1946462bdfacdcd7eb22a99f89b6ab59a90df51180d346e929fd6e
Tx public key: d576f686d4060cf5d496112e0c4005e244f3f4ffc6e255b39593fae2622af5d2
Timestamp: 1753161706 Timestamp [UCT]: 2025-07-22 05:21:46 Age [y:d:h:m:s]: 00:128:17:11:40
Block: 1330735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90829 RingCT/type: yes/0
Extra: 01d576f686d4060cf5d496112e0c4005e244f3f4ffc6e255b39593fae2622af5d2021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f43cab739bc3042e70820e95f43309e2d0a5706a76d04ec940f8ad0effc90f 0.600000000000 1818528 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": 1330745, "vin": [ { "gen": { "height": 1330735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f43cab739bc3042e70820e95f43309e2d0a5706a76d04ec940f8ad0effc90f" } } ], "extra": [ 1, 213, 118, 246, 134, 212, 6, 12, 245, 212, 150, 17, 46, 12, 64, 5, 226, 68, 243, 244, 255, 198, 226, 85, 179, 149, 147, 250, 226, 98, 42, 245, 210, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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