Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271307d301db0c2fd326b6bb91870c87fd8f1f8aedcf355ea7fdab43e0ab9235

Tx prefix hash: 3feffef3fc44a3003ea9798b38ffffcf1cd3c8c64ccdb1900ac2c55a134e2e44
Tx public key: 225258e0a5a988cb17f416229610a251cf8f53e612c10a2eb3d5919541f86cbb
Timestamp: 1738277714 Timestamp [UCT]: 2025-01-30 22:55:14 Age [y:d:h:m:s]: 00:143:02:01:08
Block: 1208656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102150 RingCT/type: yes/0
Extra: 01225258e0a5a988cb17f416229610a251cf8f53e612c10a2eb3d5919541f86cbb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd6e38cfa960c1e69e3361be4ee61ad4fec6c9b32fa7c232de0a5cc9e1c1547 0.600000000000 1695389 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": 1208666, "vin": [ { "gen": { "height": 1208656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd6e38cfa960c1e69e3361be4ee61ad4fec6c9b32fa7c232de0a5cc9e1c1547" } } ], "extra": [ 1, 34, 82, 88, 224, 165, 169, 136, 203, 23, 244, 22, 34, 150, 16, 162, 81, 207, 143, 83, 230, 18, 193, 10, 46, 179, 213, 145, 149, 65, 248, 108, 187, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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