Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec6885a63adc9b49a43a9484cebf4b69c34a9a47af7bce218ffc09249255eec

Tx prefix hash: 273e56fd5528d67a7a11916a62af34138a26c45ef33de531a82eb3488d8a1f32
Tx public key: 9fa4423824678de0bb32084c9bd1f3ebad4db2cc2d0d54094244cdf123aecf23
Timestamp: 1741174153 Timestamp [UTC]: 2025-03-05 11:29:13 Age [y:d:h:m:s]: 01:261:12:07:59
Block: 1232639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450855 RingCT/type: yes/0
Extra: 019fa4423824678de0bb32084c9bd1f3ebad4db2cc2d0d54094244cdf123aecf230211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe5d5b4ca2dbc63978a9a105bcf527883ee8fbced5e8b620335a38f9f3f4aaa9 0.000600000000 1719552 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": 1232649, "vin": [ { "gen": { "height": 1232639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe5d5b4ca2dbc63978a9a105bcf527883ee8fbced5e8b620335a38f9f3f4aaa9" } } ], "extra": [ 1, 159, 164, 66, 56, 36, 103, 141, 224, 187, 50, 8, 76, 155, 209, 243, 235, 173, 77, 178, 204, 45, 13, 84, 9, 66, 68, 205, 241, 35, 174, 207, 35, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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: