Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99bfb90cb9a23d4a5ec89280e1b64336d714cbde56fbc559c1165ade7822123a

Tx prefix hash: 1fbff7e7e872c286a5ea3191d5cece5407415d5be662f4d548a2010625902067
Tx public key: cec348439de8dc4d5fe8fb742d09f24c88f5a2f559c18ccf560bce69b1f206ef
Timestamp: 1718909383 Timestamp [UCT]: 2024-06-20 18:49:43 Age [y:d:h:m:s]: 00:283:23:47:30
Block: 1048510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202936 RingCT/type: yes/0
Extra: 01cec348439de8dc4d5fe8fb742d09f24c88f5a2f559c18ccf560bce69b1f206ef02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f2aae5f2e46b740e3dfe0a44105815d193fc7ffa4697a92c0dce41609fa0af0 0.600000000000 1518595 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": 1048520, "vin": [ { "gen": { "height": 1048510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f2aae5f2e46b740e3dfe0a44105815d193fc7ffa4697a92c0dce41609fa0af0" } } ], "extra": [ 1, 206, 195, 72, 67, 157, 232, 220, 77, 95, 232, 251, 116, 45, 9, 242, 76, 136, 245, 162, 245, 89, 193, 140, 207, 86, 11, 206, 105, 177, 242, 6, 239, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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