Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac4042e025069bdad64a0b6741dddc465d99eef8b530bdbdae930dec6b82549

Tx prefix hash: d2d207e1762044bebeb017443ad69587f156e31f1deb93525b301e31aeaa1b83
Tx public key: e6c95519bc3c749e10813d4fcd027af3f1a67c978b9355124804f8e592f0c52b
Timestamp: 1705831373 Timestamp [UCT]: 2024-01-21 10:02:53 Age [y:d:h:m:s]: 01:123:18:15:12
Block: 940059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349602 RingCT/type: yes/0
Extra: 01e6c95519bc3c749e10813d4fcd027af3f1a67c978b9355124804f8e592f0c52b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36b5ae5e6ca96835e9c7e4f8b3db8612bb3d86235de294823e6bfb9d33c857ad 0.600000000000 1398193 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": 940069, "vin": [ { "gen": { "height": 940059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36b5ae5e6ca96835e9c7e4f8b3db8612bb3d86235de294823e6bfb9d33c857ad" } } ], "extra": [ 1, 230, 201, 85, 25, 188, 60, 116, 158, 16, 129, 61, 79, 205, 2, 122, 243, 241, 166, 124, 151, 139, 147, 85, 18, 72, 4, 248, 229, 146, 240, 197, 43, 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