Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9e6f2a783657f7f84f8c0d0d2c39e7eaaff9b7cbe5ff61aa55434d2e42e8aa

Tx prefix hash: c0474509c3149aacc2b2da9160f0e07fabb6beb6176fc389d2c985fe6773ac0d
Tx public key: bde912a4570426f75cccf816e6cc458ed1742e4c1dee89cb2cddc20661bd5709
Timestamp: 1574777366 Timestamp [UTC]: 2019-11-26 14:09:26 Age [y:d:h:m:s]: 06:085:10:11:58
Block: 17964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1462081 RingCT/type: yes/0
Extra: 01bde912a4570426f75cccf816e6cc458ed1742e4c1dee89cb2cddc20661bd57090211000000035d286194000000000000000000

1 output(s) for total of 0.535153894890 xmr

stealth address amount amount idx tag
00: 69861d9404076e0867b837d8d9f021b7f4cab29611c92b99b77c8f7fe84f294b 0.535153894890 26830 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": 17974, "vin": [ { "gen": { "height": 17964 } } ], "vout": [ { "amount": 535153894890, "target": { "key": "69861d9404076e0867b837d8d9f021b7f4cab29611c92b99b77c8f7fe84f294b" } } ], "extra": [ 1, 189, 233, 18, 164, 87, 4, 38, 247, 92, 204, 248, 22, 230, 204, 69, 142, 209, 116, 46, 76, 29, 238, 137, 203, 44, 221, 194, 6, 97, 189, 87, 9, 2, 17, 0, 0, 0, 3, 93, 40, 97, 148, 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