Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764e8d0abafaf933e7a3567f987ffc800eed4e42c56dedf0f01053e9a78e5d28

Tx prefix hash: 4cec722cfa9c3b8d8134050248b90ead01ec379bf0b34a7ec8860c9aee16a900
Tx public key: 047f2c821e613c515af2eb84462cd579f0f2922fe54b3beaec6f864212ea1f00
Timestamp: 1577000912 Timestamp [UCT]: 2019-12-22 07:48:32 Age [y:d:h:m:s]: 04:320:06:58:18
Block: 29509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117640 RingCT/type: yes/0
Extra: 01047f2c821e613c515af2eb84462cd579f0f2922fe54b3beaec6f864212ea1f0002110000000f4ac5aa02000000000000000000

1 output(s) for total of 490.032964782000 dcy

stealth address amount amount idx
00: 9c07a23278bc10ed74d9b654a0103c351b94f406ae1f0d3435d426cebbdae825 490.032964782000 48569 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": 29519, "vin": [ { "gen": { "height": 29509 } } ], "vout": [ { "amount": 490032964782, "target": { "key": "9c07a23278bc10ed74d9b654a0103c351b94f406ae1f0d3435d426cebbdae825" } } ], "extra": [ 1, 4, 127, 44, 130, 30, 97, 60, 81, 90, 242, 235, 132, 70, 44, 213, 121, 240, 242, 146, 47, 229, 75, 59, 234, 236, 111, 134, 66, 18, 234, 31, 0, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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