Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cfc11eb4926e458e20f1e5e4576dd91d87fd3863b4937412f3b267c5cb40b66

Tx prefix hash: 1c56079ee748973f4f4d7625e73c7842edf7432d4ab5be3520eeaeb85d20f5fa
Tx public key: b5db976e56705c9f9df337c8961a8cde57e54a40553e5fee6e29751d96ed1837
Timestamp: 1714910209 Timestamp [UCT]: 2024-05-05 11:56:49 Age [y:d:h:m:s]: 01:189:02:44:53
Block: 1015370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393775 RingCT/type: yes/0
Extra: 01b5db976e56705c9f9df337c8961a8cde57e54a40553e5fee6e29751d96ed18370211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a006111b1f23da94b30c546531316052db3457e14c7601ae8b1485d6ceea69 0.600000000000 1478715 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": 1015380, "vin": [ { "gen": { "height": 1015370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a006111b1f23da94b30c546531316052db3457e14c7601ae8b1485d6ceea69" } } ], "extra": [ 1, 181, 219, 151, 110, 86, 112, 92, 159, 157, 243, 55, 200, 150, 26, 140, 222, 87, 229, 74, 64, 85, 62, 95, 238, 110, 41, 117, 29, 150, 237, 24, 55, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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