Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c14614c0dc282aa9311b074c5a579e662ade7dc94ffeec241f03d66fe398a4e6

Tx prefix hash: 194e911c33d265db2dcff5a075d538794872c5b45049af73dc8b7ee9e478b84a
Tx public key: 279732c4d226e3b31e8cd827bfdd4dedade3dd95711903efbaa20239d34983bc
Timestamp: 1723695950 Timestamp [UCT]: 2024-08-15 04:25:50 Age [y:d:h:m:s]: 00:254:08:21:35
Block: 1088198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181682 RingCT/type: yes/0
Extra: 01279732c4d226e3b31e8cd827bfdd4dedade3dd95711903efbaa20239d34983bc02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3f9a4a03220e17de5d05f1f83b0e19fd6c7bddcfe7fdb74d38d24b641a5ad8 0.600000000000 1562811 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": 1088208, "vin": [ { "gen": { "height": 1088198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3f9a4a03220e17de5d05f1f83b0e19fd6c7bddcfe7fdb74d38d24b641a5ad8" } } ], "extra": [ 1, 39, 151, 50, 196, 210, 38, 227, 179, 30, 140, 216, 39, 191, 221, 77, 237, 173, 227, 221, 149, 113, 25, 3, 239, 186, 162, 2, 57, 211, 73, 131, 188, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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