Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c2cea07dc6ed66065447fb75a552e4c68f96ff971cf92e524ad0034dad26ac7

Tx prefix hash: 38916cf7536d20c863a036c0dd0dbdf522b3850df911f37c742a3503e0698226
Tx public key: a147bfc63ade860cf590920891254c7e81292533730d5a9f9d1bbc12092c923d
Timestamp: 1769822719 Timestamp [UTC]: 2026-01-31 01:25:19 Age [y:d:h:m:s]: 00:295:12:36:38
Block: 1467276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216218 RingCT/type: yes/0
Extra: 01a147bfc63ade860cf590920891254c7e81292533730d5a9f9d1bbc12092c923d02110000000849d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7fc977290902069e9b85bce6443c6e6b7e71a06bb9511c4bd8ba7ead80fe50cf 0.000600000000 1956516 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": 1467286, "vin": [ { "gen": { "height": 1467276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fc977290902069e9b85bce6443c6e6b7e71a06bb9511c4bd8ba7ead80fe50cf" } } ], "extra": [ 1, 161, 71, 191, 198, 58, 222, 134, 12, 245, 144, 146, 8, 145, 37, 76, 126, 129, 41, 37, 51, 115, 13, 90, 159, 157, 27, 188, 18, 9, 44, 146, 61, 2, 17, 0, 0, 0, 8, 73, 215, 62, 152, 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: