Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be0b36c1803cf65a2affbaa29438ca75d6f9a07f1c09f7b774b8ff51ff4c9a83

Tx prefix hash: d73c043b25bb944b3154e8a8c7b4a45cc962b37fe4e286d4fe1aeb2006b96580
Tx public key: 4f0f7c328baaac608702196c4eec2577a0147d033e51259030cc4348315f9172
Timestamp: 1639336732 Timestamp [UCT]: 2021-12-12 19:18:52 Age [y:d:h:m:s]: 03:027:08:33:17
Block: 394104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798520 RingCT/type: yes/0
Extra: 014f0f7c328baaac608702196c4eec2577a0147d033e51259030cc4348315f9172021100000011de12510f000000000000000000

1 output(s) for total of 30.350804530000 dcy

stealth address amount amount idx
00: 46490460657e0fa46668513473f13f20411d05323b7d507f54a94d0d69c7c7f4 30.350804530000 791565 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": 394114, "vin": [ { "gen": { "height": 394104 } } ], "vout": [ { "amount": 30350804530, "target": { "key": "46490460657e0fa46668513473f13f20411d05323b7d507f54a94d0d69c7c7f4" } } ], "extra": [ 1, 79, 15, 124, 50, 139, 170, 172, 96, 135, 2, 25, 108, 78, 236, 37, 119, 160, 20, 125, 3, 62, 81, 37, 144, 48, 204, 67, 72, 49, 95, 145, 114, 2, 17, 0, 0, 0, 17, 222, 18, 81, 15, 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