Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 386fc588cbfe35c985ceb8867bed4763e9e86e006e4dbdb729aafdc0dffcafca

Tx prefix hash: f019ce0c06db89a1b1e566a595b32b8263f56f8822dc99489a93c5fd24691d0b
Tx public key: dcf6ebcad01693dc2012fd8d6aff0bbbbeb5b556f8e33b58e4a92d73898c3c55
Timestamp: 1730051343 Timestamp [UCT]: 2024-10-27 17:49:03 Age [y:d:h:m:s]: 00:154:17:37:04
Block: 1140849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110383 RingCT/type: yes/0
Extra: 01dcf6ebcad01693dc2012fd8d6aff0bbbbeb5b556f8e33b58e4a92d73898c3c55021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a12f1b401b4c84a8e3ad6e018803ddd49f8261ab22cd3eb6c178e95c2759aee 0.600000000000 1624652 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": 1140859, "vin": [ { "gen": { "height": 1140849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a12f1b401b4c84a8e3ad6e018803ddd49f8261ab22cd3eb6c178e95c2759aee" } } ], "extra": [ 1, 220, 246, 235, 202, 208, 22, 147, 220, 32, 18, 253, 141, 106, 255, 11, 187, 190, 181, 181, 86, 248, 227, 59, 88, 228, 169, 45, 115, 137, 140, 60, 85, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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