Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d348e57551274659508014302d58e8e1a6497a43f53e9af878e6d4b89e49880

Tx prefix hash: b07b5d29c6ca1475fbd15977ce676b2ac103ab0f86d6d9f314895e2cc7f537e9
Tx public key: 90c42890f9530587609fb9f0df85e91a323fef61796908b2d58f1f552b75e116
Timestamp: 1719618022 Timestamp [UCT]: 2024-06-28 23:40:22 Age [y:d:h:m:s]: 00:275:17:43:09
Block: 1054388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197020 RingCT/type: yes/0
Extra: 0190c42890f9530587609fb9f0df85e91a323fef61796908b2d58f1f552b75e1160211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f8ee410f229e075a8a6b9c602d46c919ae2b879fe49b003d1ab76334fa8ca8 0.600000000000 1524749 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": 1054398, "vin": [ { "gen": { "height": 1054388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f8ee410f229e075a8a6b9c602d46c919ae2b879fe49b003d1ab76334fa8ca8" } } ], "extra": [ 1, 144, 196, 40, 144, 249, 83, 5, 135, 96, 159, 185, 240, 223, 133, 233, 26, 50, 63, 239, 97, 121, 105, 8, 178, 213, 143, 31, 85, 43, 117, 225, 22, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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