Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f562927c1c80333da3b5dcb951edb1b2ed1a7f3ed08824a0de3e5c4f6680fefd

Tx prefix hash: dd4d5ae2cb5b04161b31983982d1de5429f152edff81b24957d21c798626508e
Tx public key: f12187229399fb7779d50468f17233639a8fc4c897a590141d88a7eb51037ec3
Timestamp: 1694245838 Timestamp [UCT]: 2023-09-09 07:50:38 Age [y:d:h:m:s]: 01:236:02:26:17
Block: 844219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429869 RingCT/type: yes/0
Extra: 01f12187229399fb7779d50468f17233639a8fc4c897a590141d88a7eb51037ec302110000000933af99f4000000000000000000

1 output(s) for total of 0.978930965000 dcy

stealth address amount amount idx
00: b96f1e33080f9924f5398e1f3b7790b3cba74ba70a551be7beffcbc46e608840 0.978930965000 1297515 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": 844229, "vin": [ { "gen": { "height": 844219 } } ], "vout": [ { "amount": 978930965, "target": { "key": "b96f1e33080f9924f5398e1f3b7790b3cba74ba70a551be7beffcbc46e608840" } } ], "extra": [ 1, 241, 33, 135, 34, 147, 153, 251, 119, 121, 213, 4, 104, 241, 114, 51, 99, 154, 143, 196, 200, 151, 165, 144, 20, 29, 136, 167, 235, 81, 3, 126, 195, 2, 17, 0, 0, 0, 9, 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