Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aababbd5422d29f7e7a81801a7740fc9b17ed5c66289e22d1e182678a66afdec

Tx prefix hash: 56c82644de229d3e916d441d88e54002c1bee23da227effa6c3411411f867439
Tx public key: b034ea85901faa2efd82d5ec8a0c1beac3d2adb7957a84f62a6c3fcc7145f4d6
Timestamp: 1709770263 Timestamp [UCT]: 2024-03-07 00:11:03 Age [y:d:h:m:s]: 01:053:02:55:51
Block: 972751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298984 RingCT/type: yes/0
Extra: 01b034ea85901faa2efd82d5ec8a0c1beac3d2adb7957a84f62a6c3fcc7145f4d602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34dd370e0103e37a572ea7eb983272d7bf5f35120ecc694a22e622ffba77f4fa 0.600000000000 1432670 of 15

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": 972761, "vin": [ { "gen": { "height": 972751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34dd370e0103e37a572ea7eb983272d7bf5f35120ecc694a22e622ffba77f4fa" } } ], "extra": [ 1, 176, 52, 234, 133, 144, 31, 170, 46, 253, 130, 213, 236, 138, 12, 27, 234, 195, 210, 173, 183, 149, 122, 132, 246, 42, 108, 63, 204, 113, 69, 244, 214, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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