Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394c0f29800664dbef686c242bdc67feb57373e73b3bfea447a5304b662d0616

Tx prefix hash: 47f5892930ce817d69ca668e6861afd2a821e6661952d43cb5bc7f47723ac96b
Tx public key: fc4d6ab57b5fa2f38b5664db0fa8dfc2ff316cb1a6a7a6c51442569e7b696b4b
Timestamp: 1764199598 Timestamp [UCT]: 2025-11-26 23:26:38 Age [y:d:h:m:s]: 00:001:05:23:59
Block: 1420865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 875 RingCT/type: yes/0
Extra: 01fc4d6ab57b5fa2f38b5664db0fa8dfc2ff316cb1a6a7a6c51442569e7b696b4b0211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0182dc212321782451e8fb7d0f858b465ad56a872a72b64243f8dbba1aabb6 0.600000000000 1909418 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": 1420875, "vin": [ { "gen": { "height": 1420865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0182dc212321782451e8fb7d0f858b465ad56a872a72b64243f8dbba1aabb6" } } ], "extra": [ 1, 252, 77, 106, 181, 123, 95, 162, 243, 139, 86, 100, 219, 15, 168, 223, 194, 255, 49, 108, 177, 166, 167, 166, 197, 20, 66, 86, 158, 123, 105, 107, 75, 2, 17, 0, 0, 0, 2, 78, 123, 252, 9, 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