Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d3fdc0aa39989190609e6c2fc9dcd11fd87a52f7d5abf14fba8a41a70a1226

Tx prefix hash: 635fd9cb90c7a952027265866821953fd811e89ebbc72183b66959bdb31019ee
Tx public key: d8f9a8e541d52801f89a98b690798cd71be9faa8e8cbe1543604eda89bc6b5b6
Timestamp: 1679913554 Timestamp [UCT]: 2023-03-27 10:39:14 Age [y:d:h:m:s]: 01:291:18:35:37
Block: 726120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469399 RingCT/type: yes/0
Extra: 01d8f9a8e541d52801f89a98b690798cd71be9faa8e8cbe1543604eda89bc6b5b60211000000015029cbac000000000000000000

1 output(s) for total of 2.410256437000 dcy

stealth address amount amount idx
00: b24fa628f39b45554c628dd70a62282075844dcd9b84fbfadd0bccf2c0b46ae6 2.410256437000 1171345 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": 726130, "vin": [ { "gen": { "height": 726120 } } ], "vout": [ { "amount": 2410256437, "target": { "key": "b24fa628f39b45554c628dd70a62282075844dcd9b84fbfadd0bccf2c0b46ae6" } } ], "extra": [ 1, 216, 249, 168, 229, 65, 213, 40, 1, 248, 154, 152, 182, 144, 121, 140, 215, 27, 233, 250, 168, 232, 203, 225, 84, 54, 4, 237, 168, 155, 198, 181, 182, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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