Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e34926235fb7e9865a35c768e9db615fe79e2bf6e0d6e0094fcce0beaa90462a

Tx prefix hash: ab191cf1071b68b29fb53014984bffbb9ca2e0ccea01830d8c50d2bab1ae00ab
Tx public key: e5913570e23d9502ecb32acaf8e0dfbfa517bb720a079f1e3fc14060d4dd5abe
Timestamp: 1648030758 Timestamp [UCT]: 2022-03-23 10:19:18 Age [y:d:h:m:s]: 02:360:01:18:06
Block: 464604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776644 RingCT/type: yes/0
Extra: 01e5913570e23d9502ecb32acaf8e0dfbfa517bb720a079f1e3fc14060d4dd5abe021100000004d3fcec30000000000000000000

1 output(s) for total of 17.724514133000 dcy

stealth address amount amount idx
00: 314de212fba8ba25be32dbaf60c8c94e5bb4eef84f55ee16cd75bdc9017b6707 17.724514133000 882527 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": 464614, "vin": [ { "gen": { "height": 464604 } } ], "vout": [ { "amount": 17724514133, "target": { "key": "314de212fba8ba25be32dbaf60c8c94e5bb4eef84f55ee16cd75bdc9017b6707" } } ], "extra": [ 1, 229, 145, 53, 112, 226, 61, 149, 2, 236, 179, 42, 202, 248, 224, 223, 191, 165, 23, 187, 114, 10, 7, 159, 30, 63, 193, 64, 96, 212, 221, 90, 190, 2, 17, 0, 0, 0, 4, 211, 252, 236, 48, 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