Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c2af9805ecf746c545e287f1d01908032ea39530da08b18cb956dec8bc940d

Tx prefix hash: 72fa7955d66b7876ddfa14d83346d2f1d72888bef55cfa8eb8c826b70ec829a0
Tx public key: a4b8122ba960263ad96d287fcb6843fb31e83e54a6580b72d65ed524ae1f059d
Timestamp: 1705636267 Timestamp [UTC]: 2024-01-19 03:51:07 Age [y:d:h:m:s]: 02:308:10:36:44
Block: 938450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745044 RingCT/type: yes/0
Extra: 01a4b8122ba960263ad96d287fcb6843fb31e83e54a6580b72d65ed524ae1f059d02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd5e98fc10328c3cb7f79ce3e217803d43c061489308ae9a4db3408274d94f99 0.000600000000 1396520 of 15 -

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": 938460, "vin": [ { "gen": { "height": 938450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd5e98fc10328c3cb7f79ce3e217803d43c061489308ae9a4db3408274d94f99" } } ], "extra": [ 1, 164, 184, 18, 43, 169, 96, 38, 58, 217, 109, 40, 127, 203, 104, 67, 251, 49, 232, 62, 84, 166, 88, 11, 114, 214, 94, 213, 36, 174, 31, 5, 157, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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: