Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0a3548a4b78df1fceeb6e2aba59f69849aa8479c90f875fb640406a4655555

Tx prefix hash: 2fafac4f7e244d9c30d3bd27794ee66ec6a87c62508d070d95778d667ad16a84
Tx public key: 4a9182a958f3bc803ae7ed7d5e9130f8c752f2c5a52596cdd28d87c16ab82496
Timestamp: 1634588965 Timestamp [UCT]: 2021-10-18 20:29:25 Age [y:d:h:m:s]: 03:070:16:53:12
Block: 355762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 828560 RingCT/type: yes/0
Extra: 014a9182a958f3bc803ae7ed7d5e9130f8c752f2c5a52596cdd28d87c16ab8249602110000002e37cb3088000000000000000000

1 output(s) for total of 40.664292941000 dcy

stealth address amount amount idx
00: 32f1b95410d709d0b667ae661acf5533013f27be86d2a0cbfeffc4e8646e1660 40.664292941000 726174 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": 355772, "vin": [ { "gen": { "height": 355762 } } ], "vout": [ { "amount": 40664292941, "target": { "key": "32f1b95410d709d0b667ae661acf5533013f27be86d2a0cbfeffc4e8646e1660" } } ], "extra": [ 1, 74, 145, 130, 169, 88, 243, 188, 128, 58, 231, 237, 125, 94, 145, 48, 248, 199, 82, 242, 197, 165, 37, 150, 205, 210, 141, 135, 193, 106, 184, 36, 150, 2, 17, 0, 0, 0, 46, 55, 203, 48, 136, 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