Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d7647141c39f0af139d4412931e51f95f82ce55c46e6b28a432db8ec5e3754c

Tx prefix hash: cc552713e752422abf06658fb5d2ea5c567960027607aadadc2408f8177f8842
Tx public key: ab3bcd8a105588e1d0f4adcd9a45d372923932e6ae3a76f0fef9b0e7aa2ea3f8
Timestamp: 1706300315 Timestamp [UCT]: 2024-01-26 20:18:35 Age [y:d:h:m:s]: 01:138:15:29:20
Block: 943946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360168 RingCT/type: yes/0
Extra: 01ab3bcd8a105588e1d0f4adcd9a45d372923932e6ae3a76f0fef9b0e7aa2ea3f80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6569ca062923f3a07e8edd3bfa9a00399d7bfbe87a59e9e775a5ef0552f682ea 0.600000000000 1402172 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": 943956, "vin": [ { "gen": { "height": 943946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6569ca062923f3a07e8edd3bfa9a00399d7bfbe87a59e9e775a5ef0552f682ea" } } ], "extra": [ 1, 171, 59, 205, 138, 16, 85, 136, 225, 208, 244, 173, 205, 154, 69, 211, 114, 146, 57, 50, 230, 174, 58, 118, 240, 254, 249, 176, 231, 170, 46, 163, 248, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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