Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd3a382b538153590101c0ef368e2dca4ef3a404ef2a29f483e4e10f903ada91

Tx prefix hash: 271e106e96c7fbd792662d38986bd6e09f037e857dd1fce38e6d31034584402e
Tx public key: 0f43e50bd634de1b287d5b75499e738052de110802e24f548d7ed6bbd5dd9d92
Timestamp: 1694036529 Timestamp [UCT]: 2023-09-06 21:42:09 Age [y:d:h:m:s]: 01:283:11:07:52
Block: 842487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463632 RingCT/type: yes/0
Extra: 010f43e50bd634de1b287d5b75499e738052de110802e24f548d7ed6bbd5dd9d92021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.991952562000 dcy

stealth address amount amount idx
00: 251dc088b1da81fd9ae47449217ba9e4f6aac5cc1af0c3d1815f670e41386dca 0.991952562000 1295611 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": 842497, "vin": [ { "gen": { "height": 842487 } } ], "vout": [ { "amount": 991952562, "target": { "key": "251dc088b1da81fd9ae47449217ba9e4f6aac5cc1af0c3d1815f670e41386dca" } } ], "extra": [ 1, 15, 67, 229, 11, 214, 52, 222, 27, 40, 125, 91, 117, 73, 158, 115, 128, 82, 222, 17, 8, 2, 226, 79, 84, 141, 126, 214, 187, 213, 221, 157, 146, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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