Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7fd5ef637251cd8672d7eba82d33065cfdd45110044370092aa045d2191603a

Tx prefix hash: 79053202808698617dd91a225c7b5dc0519207d5b7f70ab51ba6662d35dc9e98
Tx public key: f5e386e0dcf628005d3cbcc14583fb5e167d1e9fc62f60bc6bddc5c09d4ddd99
Timestamp: 1729987439 Timestamp [UCT]: 2024-10-27 00:03:59 Age [y:d:h:m:s]: 00:119:03:39:27
Block: 1140331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84905 RingCT/type: yes/0
Extra: 01f5e386e0dcf628005d3cbcc14583fb5e167d1e9fc62f60bc6bddc5c09d4ddd99021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575a334f6cbbf86e3c5cb7663cf06d1e6f984452262c33328bac61381803a351 0.600000000000 1624126 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": 1140341, "vin": [ { "gen": { "height": 1140331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575a334f6cbbf86e3c5cb7663cf06d1e6f984452262c33328bac61381803a351" } } ], "extra": [ 1, 245, 227, 134, 224, 220, 246, 40, 0, 93, 60, 188, 193, 69, 131, 251, 94, 22, 125, 30, 159, 198, 47, 96, 188, 107, 221, 197, 192, 157, 77, 221, 153, 2, 17, 0, 0, 0, 1, 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