Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 458196da4393bd82f4f176221db1f1f0b32be8ff2a8b8016366aa653912a99bc

Tx prefix hash: f4059c7fd038336cb37644ed9085b99cfa46a19d9076bd9a7913844c478eba8f
Tx public key: 14d04519efeb903598a5ecc584f5582f7ae798f186518958e8cbf5c9c049fc80
Timestamp: 1735905974 Timestamp [UCT]: 2025-01-03 12:06:14 Age [y:d:h:m:s]: 00:164:02:16:51
Block: 1189320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116976 RingCT/type: yes/0
Extra: 0114d04519efeb903598a5ecc584f5582f7ae798f186518958e8cbf5c9c049fc800211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d274ee3ed282585dfa8c6a43f12aa2b51ae0709c612b0e35f20771317bfad12a 0.600000000000 1675827 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": 1189330, "vin": [ { "gen": { "height": 1189320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d274ee3ed282585dfa8c6a43f12aa2b51ae0709c612b0e35f20771317bfad12a" } } ], "extra": [ 1, 20, 208, 69, 25, 239, 235, 144, 53, 152, 165, 236, 197, 132, 245, 88, 47, 122, 231, 152, 241, 134, 81, 137, 88, 232, 203, 245, 201, 192, 73, 252, 128, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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