Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe808242cc875b68908d47c40f55094150298fcb27f986cdbcb433777e4f2cb

Tx prefix hash: f1facfc4f319d99b94a69a0e80828fdb3a6623b6fdbd806d614f53cd6f041765
Tx public key: 0aa6df36c0609fb1ba6d57bed260faf20f2932793b21d09ad36714316255b5ae
Timestamp: 1766549639 Timestamp [UTC]: 2025-12-24 04:13:59 Age [y:d:h:m:s]: 00:244:05:35:43
Block: 1440324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180280 RingCT/type: yes/0
Extra: 010aa6df36c0609fb1ba6d57bed260faf20f2932793b21d09ad36714316255b5ae021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fbc9b7598d1ed6030501e1ce3a17b19225e1ec8a805436c092683e78646f00bb 0.000600000000 1929189 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": 1440334, "vin": [ { "gen": { "height": 1440324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbc9b7598d1ed6030501e1ce3a17b19225e1ec8a805436c092683e78646f00bb" } } ], "extra": [ 1, 10, 166, 223, 54, 192, 96, 159, 177, 186, 109, 87, 190, 210, 96, 250, 242, 15, 41, 50, 121, 59, 33, 208, 154, 211, 103, 20, 49, 98, 85, 181, 174, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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: