Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f79366d4f0072ea61e3dd6f656fc946d6f8da6eefc7291c9217ae79f7b44bb1

Tx prefix hash: 6e37157bf4e2a7ed4d7e5739bd22c068610d9e557385dccd5329eab79f39eeed
Tx public key: f87dc644fbc96094e2616ab73a20aa5dc005a59be88d0075fb6697111d7f6697
Timestamp: 1674274416 Timestamp [UCT]: 2023-01-21 04:13:36 Age [y:d:h:m:s]: 01:364:16:21:37
Block: 679334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521615 RingCT/type: yes/0
Extra: 01f87dc644fbc96094e2616ab73a20aa5dc005a59be88d0075fb6697111d7f66970211000000045029cbac000000000000000000

1 output(s) for total of 3.444168549000 dcy

stealth address amount amount idx
00: 010bd936fb26a723c8e6e1622e40a548ce6ceec3fe68cfa391bf7044ead1bdd6 3.444168549000 1121307 of 0

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": 679344, "vin": [ { "gen": { "height": 679334 } } ], "vout": [ { "amount": 3444168549, "target": { "key": "010bd936fb26a723c8e6e1622e40a548ce6ceec3fe68cfa391bf7044ead1bdd6" } } ], "extra": [ 1, 248, 125, 198, 68, 251, 201, 96, 148, 226, 97, 106, 183, 58, 32, 170, 93, 192, 5, 165, 155, 232, 141, 0, 117, 251, 102, 151, 17, 29, 127, 102, 151, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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