Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dada9166e546cdc213fff936f3740f65cd03c8be12672acc68f8b9ecfa30209d

Tx prefix hash: 154f9eb2bbafb9063a905b3ccddc915810a9dbf3a6d6707f43c1fbc6d69c9fe8
Tx public key: 2a3fba29e94cfc222869baea021dd9064b7e326e3ef017fe410c8f5dbfd77a01
Timestamp: 1626713600 Timestamp [UTC]: 2021-07-19 16:53:20 Age [y:d:h:m:s]: 04:220:23:08:05
Block: 297050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187841 RingCT/type: yes/0
Extra: 012a3fba29e94cfc222869baea021dd9064b7e326e3ef017fe410c8f5dbfd77a0102110000009a04712537000000000000000000

1 output(s) for total of 0.063645183923 xmr

stealth address amount amount idx tag
00: 82aabce3173bab2b642b35c9706363682fc4d226e7b49b5ab9a0d8acea67caba 0.063645183923 621776 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": 297060, "vin": [ { "gen": { "height": 297050 } } ], "vout": [ { "amount": 63645183923, "target": { "key": "82aabce3173bab2b642b35c9706363682fc4d226e7b49b5ab9a0d8acea67caba" } } ], "extra": [ 1, 42, 63, 186, 41, 233, 76, 252, 34, 40, 105, 186, 234, 2, 29, 217, 6, 75, 126, 50, 110, 62, 240, 23, 254, 65, 12, 143, 93, 191, 215, 122, 1, 2, 17, 0, 0, 0, 154, 4, 113, 37, 55, 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