Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed394044186d60ffef404644a2ad923dcf1e470d5206bac81cfd8ffbc7d3e321

Tx prefix hash: a107f5118287b7434920774a9e73ee78265163c9ecc50e2be35c5cf79a132e3c
Tx public key: c2c00b4bc8802c0410b4ac60344d41c7a1f994d23958ac51428a7c77e588c364
Timestamp: 1717285160 Timestamp [UCT]: 2024-06-01 23:39:20 Age [y:d:h:m:s]: 00:309:21:49:17
Block: 1035054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221469 RingCT/type: yes/0
Extra: 01c2c00b4bc8802c0410b4ac60344d41c7a1f994d23958ac51428a7c77e588c364021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 002b7b5415ff62cdf2edb2a4b1c3c0c1ce42d4f30f041889fa64ab9bbc774845 0.600000000000 1503573 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": 1035064, "vin": [ { "gen": { "height": 1035054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "002b7b5415ff62cdf2edb2a4b1c3c0c1ce42d4f30f041889fa64ab9bbc774845" } } ], "extra": [ 1, 194, 192, 11, 75, 200, 128, 44, 4, 16, 180, 172, 96, 52, 77, 65, 199, 161, 249, 148, 210, 57, 88, 172, 81, 66, 138, 124, 119, 229, 136, 195, 100, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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