Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d06cf6eaac6d27e4f0ed2124388f65d6a2ac22493c0ceadfdb0a7365250cc65

Tx prefix hash: 0eea34d793589acbe4a07a5b19b6c9f4f710d15d21d095c38e88f4264632d71c
Tx public key: 55cbb39879f1fb63d02e9d34f90d26eab66b79ee610e33d62f1fd864a2b568f8
Timestamp: 1719090910 Timestamp [UCT]: 2024-06-22 21:15:10 Age [y:d:h:m:s]: 01:147:00:59:04
Block: 1050002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363667 RingCT/type: yes/0
Extra: 0155cbb39879f1fb63d02e9d34f90d26eab66b79ee610e33d62f1fd864a2b568f8021100000002c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652b367e1e2514970d489f628715ac6db00c375091a7dfcb9d1789b054e007f6 0.600000000000 1520139 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": 1050012, "vin": [ { "gen": { "height": 1050002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652b367e1e2514970d489f628715ac6db00c375091a7dfcb9d1789b054e007f6" } } ], "extra": [ 1, 85, 203, 179, 152, 121, 241, 251, 99, 208, 46, 157, 52, 249, 13, 38, 234, 182, 107, 121, 238, 97, 14, 51, 214, 47, 31, 216, 100, 162, 181, 104, 248, 2, 17, 0, 0, 0, 2, 197, 249, 207, 208, 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