Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51beba57fcfcfe6090854f3fa6304a7e237c5e3bb1c9af80f5afd3a12d31213d

Tx prefix hash: 6ce007dfbec0570e682693119d16aa6ab2fda96e26abc587db2bc998dc7978a6
Tx public key: 5055776fb5ae1d98e900dfda60b8dc38c723868792b4c92bddb8fce820b1ffe0
Timestamp: 1648706173 Timestamp [UTC]: 2022-03-31 05:56:13 Age [y:d:h:m:s]: 04:043:00:56:22
Block: 470100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1061817 RingCT/type: yes/0
Extra: 015055776fb5ae1d98e900dfda60b8dc38c723868792b4c92bddb8fce820b1ffe0021100000003a272b9cb000000000000000000

1 output(s) for total of 0.016996668400 xmr

stealth address amount amount idx tag
00: f60c6a5e9e1a0f6968284037a4f2aa5a6ace96f706a24b3a5fed3ff46fa82bb3 0.016996668400 889180 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": 470110, "vin": [ { "gen": { "height": 470100 } } ], "vout": [ { "amount": 16996668400, "target": { "key": "f60c6a5e9e1a0f6968284037a4f2aa5a6ace96f706a24b3a5fed3ff46fa82bb3" } } ], "extra": [ 1, 80, 85, 119, 111, 181, 174, 29, 152, 233, 0, 223, 218, 96, 184, 220, 56, 199, 35, 134, 135, 146, 180, 201, 43, 221, 184, 252, 232, 32, 177, 255, 224, 2, 17, 0, 0, 0, 3, 162, 114, 185, 203, 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) | monero version: