Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 423ede45face2174280cee2fd1bb8f85bce7439cb94c54e65bb8a37ca0c63ef6

Tx prefix hash: a83e21efb252e8a6d8697dbe524afdfe8d3f5e04f9ac7d10e622c98b5ce51e43
Tx public key: 25461754f94239f7b2b32c799f709a0bf74496bb11b82455ad5cfdbc6cc577fd
Timestamp: 1722103629 Timestamp [UCT]: 2024-07-27 18:07:09 Age [y:d:h:m:s]: 00:183:04:52:54
Block: 1074997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130914 RingCT/type: yes/0
Extra: 0125461754f94239f7b2b32c799f709a0bf74496bb11b82455ad5cfdbc6cc577fd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0487b710b97937b1ba6cc0f94331d48c46d0f626bfab290df4d1f9a4122bb83a 0.600000000000 1547516 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": 1075007, "vin": [ { "gen": { "height": 1074997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0487b710b97937b1ba6cc0f94331d48c46d0f626bfab290df4d1f9a4122bb83a" } } ], "extra": [ 1, 37, 70, 23, 84, 249, 66, 57, 247, 178, 179, 44, 121, 159, 112, 154, 11, 247, 68, 150, 187, 17, 184, 36, 85, 173, 92, 253, 188, 108, 197, 119, 253, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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