Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2575ef2e056fc07cc632bf88475cc89a609d1a3cf785671b2606aae9931c061

Tx prefix hash: 7a5df66f224925f50f6e03a6c9e2425d738b7c88454daac9fd67035e3fb7b0c9
Tx public key: 868f1c83fd0328c2f2e2b910942beef37930de6bd5c5ca9fb7194e8f127fc62e
Timestamp: 1772811099 Timestamp [UTC]: 2026-03-06 15:31:39 Age [y:d:h:m:s]: 00:067:07:44:57
Block: 1492024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40400 RingCT/type: yes/0
Extra: 01868f1c83fd0328c2f2e2b910942beef37930de6bd5c5ca9fb7194e8f127fc62e021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb90c4f4daa7e5cc051524448c5070d4e6ce3ef0553fd0cb849f6adf5268f583 0.000600000000 1981562 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": 1492034, "vin": [ { "gen": { "height": 1492024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb90c4f4daa7e5cc051524448c5070d4e6ce3ef0553fd0cb849f6adf5268f583" } } ], "extra": [ 1, 134, 143, 28, 131, 253, 3, 40, 194, 242, 226, 185, 16, 148, 43, 238, 243, 121, 48, 222, 107, 213, 197, 202, 159, 183, 25, 78, 143, 18, 127, 198, 46, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: