Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d32b6f44a654a528a3b2745a949efd7c09b64c214cb90f6327c9c230cda48b

Tx prefix hash: 976a9742618d7f3f0747d25405a60af56a3cdd274e2bddbd670bd5000d088d8d
Tx public key: a4073b0ef5e42544157307f071486f869f88facb5f32da4833dc536f2f96b123
Timestamp: 1746010633 Timestamp [UCT]: 2025-04-30 10:57:13 Age [y:d:h:m:s]: 00:204:22:38:37
Block: 1272710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144146 RingCT/type: yes/0
Extra: 01a4073b0ef5e42544157307f071486f869f88facb5f32da4833dc536f2f96b12302110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cfa0e0df43a9c679babdb3a0bb1a83969e715299b2a3367e6b057742a2b219a 0.600000000000 1759985 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": 1272720, "vin": [ { "gen": { "height": 1272710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cfa0e0df43a9c679babdb3a0bb1a83969e715299b2a3367e6b057742a2b219a" } } ], "extra": [ 1, 164, 7, 59, 14, 245, 228, 37, 68, 21, 115, 7, 240, 113, 72, 111, 134, 159, 136, 250, 203, 95, 50, 218, 72, 51, 220, 83, 111, 47, 150, 177, 35, 2, 17, 0, 0, 0, 4, 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