Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c63980b3662a30a61e6ed9415b5dc8769f7c28e865d00b3b1f9312122b7cb48

Tx prefix hash: 42d9771ece193c4772177aab50cf9eb4aff41c17a816c4bfb3235c3c66048f1d
Tx public key: b9f0f60a35e3a057f424f307eb861ab5bbe8f11b2a837417e1a46198be33876a
Timestamp: 1702290230 Timestamp [UCT]: 2023-12-11 10:23:50 Age [y:d:h:m:s]: 01:333:12:32:47
Block: 910737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497221 RingCT/type: yes/0
Extra: 01b9f0f60a35e3a057f424f307eb861ab5bbe8f11b2a837417e1a46198be33876a02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18fe726de954c3f09f7e7776d9dae807564b03076738b0c22d709ab15757fc8e 0.600000000000 1367904 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": 910747, "vin": [ { "gen": { "height": 910737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18fe726de954c3f09f7e7776d9dae807564b03076738b0c22d709ab15757fc8e" } } ], "extra": [ 1, 185, 240, 246, 10, 53, 227, 160, 87, 244, 36, 243, 7, 235, 134, 26, 181, 187, 232, 241, 27, 42, 131, 116, 23, 225, 164, 97, 152, 190, 51, 135, 106, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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