Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77b161805bbe165a0049e91e98cafa29c3a47bfa46292e6060fb78e792b93b2f

Tx prefix hash: b86589e0c5ca157c5580738d7c16e261d1e7279abb15023c0b38ad00e27f158f
Tx public key: e269e142ca5aed7d2b6868aabc3d47cc617e364fb73508022d77a53d30f8a4ee
Timestamp: 1577908856 Timestamp [UCT]: 2020-01-01 20:00:56 Age [y:d:h:m:s]: 05:134:21:49:38
Block: 36578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1246331 RingCT/type: yes/0
Extra: 01e269e142ca5aed7d2b6868aabc3d47cc617e364fb73508022d77a53d30f8a4ee0211000000104ac5aa02000000000000000000

1 output(s) for total of 464.304351999000 dcy

stealth address amount amount idx
00: 1411e7db1ab6dae5fabf5a148afc08cb64df5a2c374daa494bed598b1d69af95 464.304351999000 61989 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": 36588, "vin": [ { "gen": { "height": 36578 } } ], "vout": [ { "amount": 464304351999, "target": { "key": "1411e7db1ab6dae5fabf5a148afc08cb64df5a2c374daa494bed598b1d69af95" } } ], "extra": [ 1, 226, 105, 225, 66, 202, 90, 237, 125, 43, 104, 104, 170, 188, 61, 71, 204, 97, 126, 54, 79, 183, 53, 8, 2, 45, 119, 165, 61, 48, 248, 164, 238, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 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