Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5bd4d3b4dc3975ec235483d69165fd5aa70403f43f6c7459329e7f1278441b6

Tx prefix hash: fcf83ac17541903226c440868bd9b25d2e426c3bc7fbbdb8f5846e1403e13e8b
Tx public key: 2b2c2e00f7f0a9d804f8f56bf55cb0e74daa0c0c4ba140043e033ab71a307afc
Timestamp: 1696529925 Timestamp [UCT]: 2023-10-05 18:18:45 Age [y:d:h:m:s]: 01:099:15:39:32
Block: 863176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332489 RingCT/type: yes/0
Extra: 012b2c2e00f7f0a9d804f8f56bf55cb0e74daa0c0c4ba140043e033ab71a307afc02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.847109648000 dcy

stealth address amount amount idx
00: b969f59b4d9726371e0ccde0b1f83bec8a0059e43b88cf31fff754441f0c7d75 0.847109648000 1317624 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": 863186, "vin": [ { "gen": { "height": 863176 } } ], "vout": [ { "amount": 847109648, "target": { "key": "b969f59b4d9726371e0ccde0b1f83bec8a0059e43b88cf31fff754441f0c7d75" } } ], "extra": [ 1, 43, 44, 46, 0, 247, 240, 169, 216, 4, 248, 245, 107, 245, 92, 176, 231, 77, 170, 12, 12, 75, 161, 64, 4, 62, 3, 58, 183, 26, 48, 122, 252, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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