Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8473c3a7e3b3b47926493113c24df56aed233b2cb8a15723f6807206c5da7c3

Tx prefix hash: 0a2cdbb3f161e5f5b1c4ed49fdb5ee0d5692ebced985fb76e4bbe697dc714546
Tx public key: cf10930719cc799b0180c1966e948bfdd8c2bf8bc1d7f1664c64d9491a008f9a
Timestamp: 1723266821 Timestamp [UCT]: 2024-08-10 05:13:41 Age [y:d:h:m:s]: 00:106:13:49:55
Block: 1084639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76242 RingCT/type: yes/0
Extra: 01cf10930719cc799b0180c1966e948bfdd8c2bf8bc1d7f1664c64d9491a008f9a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 099effd89ab5aa3368522141c7ca4159631ca2f534dc02ce7b9b68bc307884a3 0.600000000000 1558988 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": 1084649, "vin": [ { "gen": { "height": 1084639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "099effd89ab5aa3368522141c7ca4159631ca2f534dc02ce7b9b68bc307884a3" } } ], "extra": [ 1, 207, 16, 147, 7, 25, 204, 121, 155, 1, 128, 193, 150, 110, 148, 139, 253, 216, 194, 191, 139, 193, 215, 241, 102, 76, 100, 217, 73, 26, 0, 143, 154, 2, 17, 0, 0, 0, 2, 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