Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1f13b42a8e7b2826a5cabc20d10eaa4a04fe99fdf0df2e38516e395f960f8d

Tx prefix hash: 3ba2ab14b04e039553aba000c9f553dc6b7fbc24f535eac1299aad3736d7752d
Tx public key: 092f1bfae2583aa8d8b850132c4a045fe980232eaf78d47ea89b143210d741f9
Timestamp: 1578465574 Timestamp [UTC]: 2020-01-08 06:39:34 Age [y:d:h:m:s]: 06:059:08:58:53
Block: 41014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1451014 RingCT/type: yes/0
Extra: 01092f1bfae2583aa8d8b850132c4a045fe980232eaf78d47ea89b143210d741f90211000000104943cd9f000000000000000000

1 output(s) for total of 0.448861066467 xmr

stealth address amount amount idx tag
00: 465c564a663cb93c41b0e4d6ca530edfdfa36b345a9908771f5fc555b376cf56 0.448861066467 72642 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": 41024, "vin": [ { "gen": { "height": 41014 } } ], "vout": [ { "amount": 448861066467, "target": { "key": "465c564a663cb93c41b0e4d6ca530edfdfa36b345a9908771f5fc555b376cf56" } } ], "extra": [ 1, 9, 47, 27, 250, 226, 88, 58, 168, 216, 184, 80, 19, 44, 74, 4, 95, 233, 128, 35, 46, 175, 120, 212, 126, 168, 155, 20, 50, 16, 215, 65, 249, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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