Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb6a676d0177d2ff774d478a6322ce0a10f6d91f82a80b67ec29bc6e63ce8e1

Tx prefix hash: 6fd28d5b5d28243de519b8ad816fba2aa4b51aae65aa15b53ec9571b6b416064
Tx public key: 47dcdc59edb5a9aa218aceae5631879dc26b704a42d304b1814b3eefe7d84c26
Timestamp: 1760905387 Timestamp [UTC]: 2025-10-19 20:23:07 Age [y:d:h:m:s]: 01:029:04:16:28
Block: 1393581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287178 RingCT/type: yes/0
Extra: 0147dcdc59edb5a9aa218aceae5631879dc26b704a42d304b1814b3eefe7d84c26021100000001df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf37b885ae7f76916dd31d5cdb286074403fb5e60c03cb5ae26410231d311791 0.000600000000 1881846 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": 1393591, "vin": [ { "gen": { "height": 1393581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf37b885ae7f76916dd31d5cdb286074403fb5e60c03cb5ae26410231d311791" } } ], "extra": [ 1, 71, 220, 220, 89, 237, 181, 169, 170, 33, 138, 206, 174, 86, 49, 135, 157, 194, 107, 112, 74, 66, 211, 4, 177, 129, 75, 62, 239, 231, 216, 76, 38, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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: