Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49123a0cfc010aae9f4c047c3b95e4bb04aba6ef558972c3f5b22d652c4668f

Tx prefix hash: 426295f9c448f0485f5d9ba98762ccf341137f4c1e31bbd50bec6052696c28cc
Tx public key: a85e3ddde56a7aa34a32b66651bbeee91c9530d4773269399e57f4d977912b31
Timestamp: 1767590199 Timestamp [UTC]: 2026-01-05 05:16:39 Age [y:d:h:m:s]: 00:321:03:51:43
Block: 1448961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234533 RingCT/type: yes/0
Extra: 01a85e3ddde56a7aa34a32b66651bbeee91c9530d4773269399e57f4d977912b3102110000000a215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1ccdf020e17daf5022853d5b899dd3674bde88de03e7a02fe229cd5d6616438 0.000600000000 1937939 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": 1448971, "vin": [ { "gen": { "height": 1448961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1ccdf020e17daf5022853d5b899dd3674bde88de03e7a02fe229cd5d6616438" } } ], "extra": [ 1, 168, 94, 61, 221, 229, 106, 122, 163, 74, 50, 182, 102, 81, 187, 238, 233, 28, 149, 48, 212, 119, 50, 105, 57, 158, 87, 244, 217, 119, 145, 43, 49, 2, 17, 0, 0, 0, 10, 33, 91, 191, 137, 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: