Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5aaf14a0b08472ff51723472c57b36bba216f67c0a83b2d671c9cf63eb565a9

Tx prefix hash: 545ead4658ab373593107d58b522fa6073463cc1d3fbe8600c8e679d66f52c00
Tx public key: 9955c3c183e01ab05b81c755e3b4a0f13b8a26194602dd2d96a40e6efd5bb344
Timestamp: 1721932280 Timestamp [UCT]: 2024-07-25 18:31:20 Age [y:d:h:m:s]: 00:098:03:04:04
Block: 1073572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70213 RingCT/type: yes/0
Extra: 019955c3c183e01ab05b81c755e3b4a0f13b8a26194602dd2d96a40e6efd5bb34402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61653bbf3d7e706dd0a69f2cca6ab3201210fa4bc84cbf04d81e731fde4bd530 0.600000000000 1546077 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": 1073582, "vin": [ { "gen": { "height": 1073572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61653bbf3d7e706dd0a69f2cca6ab3201210fa4bc84cbf04d81e731fde4bd530" } } ], "extra": [ 1, 153, 85, 195, 193, 131, 224, 26, 176, 91, 129, 199, 85, 227, 180, 160, 241, 59, 138, 38, 25, 70, 2, 221, 45, 150, 164, 14, 110, 253, 91, 179, 68, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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