Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ba7ce9af332b863f98103d9b1db26331e063eae9210d68fc93ce08360fab6ea

Tx prefix hash: 12793f3fb88f424499d94b41453e8dc0a45b593149e0c6831788bf018e327a40
Tx public key: 67b971bfbde8bb3eee5c68a91ccb0036d201229e1372aa12868a63bfe16620fe
Timestamp: 1658593196 Timestamp [UCT]: 2022-07-23 16:19:56 Age [y:d:h:m:s]: 02:296:11:43:56
Block: 550060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733141 RingCT/type: yes/0
Extra: 0167b971bfbde8bb3eee5c68a91ccb0036d201229e1372aa12868a63bfe16620fe02110000000275e3f0e9000000000000000000

1 output(s) for total of 9.234704677000 dcy

stealth address amount amount idx
00: 3e29f27ea969ef0d3a19a79d928ca3b3b1f4dd267102d6753a53d823de534eb6 9.234704677000 981497 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": 550070, "vin": [ { "gen": { "height": 550060 } } ], "vout": [ { "amount": 9234704677, "target": { "key": "3e29f27ea969ef0d3a19a79d928ca3b3b1f4dd267102d6753a53d823de534eb6" } } ], "extra": [ 1, 103, 185, 113, 191, 189, 232, 187, 62, 238, 92, 104, 169, 28, 203, 0, 54, 210, 1, 34, 158, 19, 114, 170, 18, 134, 138, 99, 191, 225, 102, 32, 254, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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