Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f95ef8439c9dda0e5e37113128d89b7b6687e172f4e21d9dd0e76fc2e64b8b

Tx prefix hash: a22fc90388396ca88baecd58a1be4407ae5d24dd7982916712986db359cd9ef0
Tx public key: ce9f324424c3fa335b941117a12b620805c0ab2882f42b03b34db38f30b84edc
Timestamp: 1698592638 Timestamp [UTC]: 2023-10-29 15:17:18 Age [y:d:h:m:s]: 02:140:15:49:36
Block: 880290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620032 RingCT/type: yes/0
Extra: 01ce9f324424c3fa335b941117a12b620805c0ab2882f42b03b34db38f30b84edc02110000000533af99f4000000000000000000

1 output(s) for total of 0.000743419274 xmr

stealth address amount amount idx tag
00: 40c6ae30cd1cadfc4ab333f166c8ce2f28a63920ecf256bf44601959fadc2652 0.000743419274 1335836 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 dinastycoin-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": 880300, "vin": [ { "gen": { "height": 880290 } } ], "vout": [ { "amount": 743419274, "target": { "key": "40c6ae30cd1cadfc4ab333f166c8ce2f28a63920ecf256bf44601959fadc2652" } } ], "extra": [ 1, 206, 159, 50, 68, 36, 195, 250, 51, 91, 148, 17, 23, 161, 43, 98, 8, 5, 192, 171, 40, 130, 244, 43, 3, 179, 77, 179, 143, 48, 184, 78, 220, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369