Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cca97f93cc85f1277905dcb2edf5692cf0922f37a233286b860b71f97c07c5d2

Tx prefix hash: 2f03099eb12b6883a28a56116b2d27f9b51234a0f977247694708180137b56a3
Tx public key: f8f1f55336b059b2d55c494583f06f3afa97028079ce8801c088c2b09f7f78d3
Timestamp: 1736064433 Timestamp [UCT]: 2025-01-05 08:07:13 Age [y:d:h:m:s]: 00:345:21:49:36
Block: 1190612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244757 RingCT/type: yes/0
Extra: 01f8f1f55336b059b2d55c494583f06f3afa97028079ce8801c088c2b09f7f78d30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0e0840ac5b723efc32f52b9b66dbf8701603b55af6cd853c5e30bea08e4b951 0.600000000000 1677129 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": 1190622, "vin": [ { "gen": { "height": 1190612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0e0840ac5b723efc32f52b9b66dbf8701603b55af6cd853c5e30bea08e4b951" } } ], "extra": [ 1, 248, 241, 245, 83, 54, 176, 89, 178, 213, 92, 73, 69, 131, 240, 111, 58, 250, 151, 2, 128, 121, 206, 136, 1, 192, 136, 194, 176, 159, 127, 120, 211, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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