Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 963dc06b900578e8b96dbb7de95c16d086b8921adb9bf358b29a930789bcf3e4

Tx prefix hash: 1f98ad8c467d6a273e334c7d5b94f834741a929dc36ac5692a58db7d17067fa2
Tx public key: 150b7be7b5cd6c3f87eddffb9e8822caf809ec27cf21eb7bc8ea751fb5286911
Timestamp: 1744101860 Timestamp [UCT]: 2025-04-08 08:44:20 Age [y:d:h:m:s]: 00:227:14:38:37
Block: 1256857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160416 RingCT/type: yes/0
Extra: 01150b7be7b5cd6c3f87eddffb9e8822caf809ec27cf21eb7bc8ea751fb52869110211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db5ed8dff68bec4c01a1a6eefd083887321354c1bfecd51c3aaeb7c98cbad66 0.600000000000 1743974 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": 1256867, "vin": [ { "gen": { "height": 1256857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db5ed8dff68bec4c01a1a6eefd083887321354c1bfecd51c3aaeb7c98cbad66" } } ], "extra": [ 1, 21, 11, 123, 231, 181, 205, 108, 63, 135, 237, 223, 251, 158, 136, 34, 202, 248, 9, 236, 39, 207, 33, 235, 123, 200, 234, 117, 31, 181, 40, 105, 17, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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