Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b768d6080f5b3043d214cead3520845ea0dafa7942e8e374ecc29eb9e6fd2263

Tx prefix hash: b236280b5ce79d1a167869c6984eeaa66b0fd89210aab4577b13fc70c38c34f8
Tx public key: cbeeda07d976685d13e5db2e5f34c8807cc1dd8b3f4edab93a7fd97dda289218
Timestamp: 1629441502 Timestamp [UCT]: 2021-08-20 06:38:22 Age [y:d:h:m:s]: 03:173:15:13:41
Block: 317538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 897535 RingCT/type: yes/0
Extra: 01cbeeda07d976685d13e5db2e5f34c8807cc1dd8b3f4edab93a7fd97dda2892180211000000e9e6f80b5a000000000000000000

1 output(s) for total of 54.433374004000 dcy

stealth address amount amount idx
00: d0ae557003a5ee58006fd85f965a58d2d2013e36a351760991ecab71455c4965 54.433374004000 660225 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": 317548, "vin": [ { "gen": { "height": 317538 } } ], "vout": [ { "amount": 54433374004, "target": { "key": "d0ae557003a5ee58006fd85f965a58d2d2013e36a351760991ecab71455c4965" } } ], "extra": [ 1, 203, 238, 218, 7, 217, 118, 104, 93, 19, 229, 219, 46, 95, 52, 200, 128, 124, 193, 221, 139, 63, 78, 218, 185, 58, 127, 217, 125, 218, 40, 146, 24, 2, 17, 0, 0, 0, 233, 230, 248, 11, 90, 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