Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de30e12f9b9cd1323a28d110bacb63c4f4497f8f1d52b7fce1b43c98c392afc1

Tx prefix hash: d70165eaa2398f1db81268eeab8955cb8dc4178c9deb6a470e9bd978bfc5e2a9
Tx public key: 43238a2f05b4d61312ec02db0156835cb6784272a03479c326c1a1f49358f13c
Timestamp: 1727463985 Timestamp [UCT]: 2024-09-27 19:06:25 Age [y:d:h:m:s]: 00:176:18:19:07
Block: 1119435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126145 RingCT/type: yes/0
Extra: 0143238a2f05b4d61312ec02db0156835cb6784272a03479c326c1a1f49358f13c02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89fc61bbce56fc169a4553b3f3f0d515b9909c31398dbaea6d7edccb0ef57760 0.600000000000 1600990 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": 1119445, "vin": [ { "gen": { "height": 1119435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89fc61bbce56fc169a4553b3f3f0d515b9909c31398dbaea6d7edccb0ef57760" } } ], "extra": [ 1, 67, 35, 138, 47, 5, 180, 214, 19, 18, 236, 2, 219, 1, 86, 131, 92, 182, 120, 66, 114, 160, 52, 121, 195, 38, 193, 161, 244, 147, 88, 241, 60, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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