Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3fa38fda3f0580c9f2dceacb354c333f33c1401c0b72d31acc8ad4eac79eac1

Tx prefix hash: b68b46f333b81540a2e9dd1a13030c1cb70f917aa3bd8aec5da39666f550a96a
Tx public key: 1ba5bfc11950a2a27bffbc6983e942c854ff0b6a3d51594e6cf8f16b650712f4
Timestamp: 1582054759 Timestamp [UCT]: 2020-02-18 19:39:19 Age [y:d:h:m:s]: 04:315:03:42:59
Block: 67709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117623 RingCT/type: yes/0
Extra: 011ba5bfc11950a2a27bffbc6983e942c854ff0b6a3d51594e6cf8f16b650712f40211000000084943cd9f000000000000000000

1 output(s) for total of 366.144725843000 dcy

stealth address amount amount idx
00: 90bb63b46cd1617003c11e2498f57f0ba44b02c3c3bed2c291b86648d23c8df3 366.144725843000 124708 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": 67719, "vin": [ { "gen": { "height": 67709 } } ], "vout": [ { "amount": 366144725843, "target": { "key": "90bb63b46cd1617003c11e2498f57f0ba44b02c3c3bed2c291b86648d23c8df3" } } ], "extra": [ 1, 27, 165, 191, 193, 25, 80, 162, 162, 123, 255, 188, 105, 131, 233, 66, 200, 84, 255, 11, 106, 61, 81, 89, 78, 108, 248, 241, 107, 101, 7, 18, 244, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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