Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c800e579a9d01748f110fd367db01b0bbe7746b2b79a0abbb881c4da3c2a78a8

Tx prefix hash: 3462a71eba8634a0b8161a75a8e3d62d30add4ebb651569f8d44fbd40c4ef3d7
Tx public key: 605fb230d0db996e538f7ab8f4c27044f18428ec2e0f0b8c81c7c5b168dfbea5
Timestamp: 1727046816 Timestamp [UCT]: 2024-09-22 23:13:36 Age [y:d:h:m:s]: 00:202:01:47:58
Block: 1115978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144238 RingCT/type: yes/0
Extra: 01605fb230d0db996e538f7ab8f4c27044f18428ec2e0f0b8c81c7c5b168dfbea502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc46f264434df1c2d69d8f4d311c5ce7f74df3dd5926efa0d588684b30ab6680 0.600000000000 1596299 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": 1115988, "vin": [ { "gen": { "height": 1115978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc46f264434df1c2d69d8f4d311c5ce7f74df3dd5926efa0d588684b30ab6680" } } ], "extra": [ 1, 96, 95, 178, 48, 208, 219, 153, 110, 83, 143, 122, 184, 244, 194, 112, 68, 241, 132, 40, 236, 46, 15, 11, 140, 129, 199, 197, 177, 104, 223, 190, 165, 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