Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f285c7c529ebb88a98dbfbf0cc4f57302bc93114e0fc51bfcf653f39498c81ed

Tx prefix hash: fbdb80267f330e426e6815897763f3a51f18b7b78f43d1f7174d9b746fa3ca0f
Tx public key: adc4507f37e1a485e23be347a9e06b5399c28185e83df522f10327a4326af289
Timestamp: 1657854998 Timestamp [UCT]: 2022-07-15 03:16:38 Age [y:d:h:m:s]: 03:108:19:05:14
Block: 543999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 857510 RingCT/type: yes/0
Extra: 01adc4507f37e1a485e23be347a9e06b5399c28185e83df522f10327a4326af289021100000013e6d27f9c000000000000000000

1 output(s) for total of 9.671762631000 dcy

stealth address amount amount idx
00: 47bad42f5a5c97c3b3a0345c95cb9bc43c536dca9e978edf78aa2fb301f827ce 9.671762631000 974734 of 0

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": 544009, "vin": [ { "gen": { "height": 543999 } } ], "vout": [ { "amount": 9671762631, "target": { "key": "47bad42f5a5c97c3b3a0345c95cb9bc43c536dca9e978edf78aa2fb301f827ce" } } ], "extra": [ 1, 173, 196, 80, 127, 55, 225, 164, 133, 226, 59, 227, 71, 169, 224, 107, 83, 153, 194, 129, 133, 232, 61, 245, 34, 241, 3, 39, 164, 50, 106, 242, 137, 2, 17, 0, 0, 0, 19, 230, 210, 127, 156, 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