Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e5d92d88d9fb851d754cc725719fc0c9ae2924e658801655bdc0230b7affa9

Tx prefix hash: 54e5c07f5f018112bf840ef9479bc63b3fc14490d925d473d00b2c6de6e45bc4
Tx public key: 2cb356f776381ae7e8e4748b5d65f4f1507b157e2e40101d1960a8bd7ca551f0
Timestamp: 1723794156 Timestamp [UCT]: 2024-08-16 07:42:36 Age [y:d:h:m:s]: 00:099:20:03:39
Block: 1089011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71418 RingCT/type: yes/0
Extra: 012cb356f776381ae7e8e4748b5d65f4f1507b157e2e40101d1960a8bd7ca551f0021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deae495939a2da3f12b8123204a7330c96b8e3789f2ed63899d04e7d81196f14 0.600000000000 1563630 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": 1089021, "vin": [ { "gen": { "height": 1089011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deae495939a2da3f12b8123204a7330c96b8e3789f2ed63899d04e7d81196f14" } } ], "extra": [ 1, 44, 179, 86, 247, 118, 56, 26, 231, 232, 228, 116, 139, 93, 101, 244, 241, 80, 123, 21, 126, 46, 64, 16, 29, 25, 96, 168, 189, 124, 165, 81, 240, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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