Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56669572112fa38fa4c87d83c1a1ba2c93e91b69352004be1fe73ae550210f28

Tx prefix hash: 3f7330cb25ef10220e6331646eb1c913122f0e98983789dbb8fcabcc9d0c9c2d
Tx public key: 063dbe645f00fe87c8a8ec7a2cdc9de8a89dcd38fca7d4aae7ff663d2d2639c7
Timestamp: 1700329693 Timestamp [UCT]: 2023-11-18 17:48:13 Age [y:d:h:m:s]: 01:142:00:39:23
Block: 894477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362678 RingCT/type: yes/0
Extra: 01063dbe645f00fe87c8a8ec7a2cdc9de8a89dcd38fca7d4aae7ff663d2d2639c702110000000233af99f4000000000000000000

1 output(s) for total of 0.667154432000 dcy

stealth address amount amount idx
00: 8a336b7bbaa5ed40f15f3666c60dd9c1bea0cec4fde6f8316967eab4c21a5a6c 0.667154432000 1350680 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": 894487, "vin": [ { "gen": { "height": 894477 } } ], "vout": [ { "amount": 667154432, "target": { "key": "8a336b7bbaa5ed40f15f3666c60dd9c1bea0cec4fde6f8316967eab4c21a5a6c" } } ], "extra": [ 1, 6, 61, 190, 100, 95, 0, 254, 135, 200, 168, 236, 122, 44, 220, 157, 232, 168, 157, 205, 56, 252, 167, 212, 170, 231, 255, 102, 61, 45, 38, 57, 199, 2, 17, 0, 0, 0, 2, 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