Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 055ef648cef85d9f461a12643b7e0c5f572ecae0d20aaa1b3e15b1ecb9db17b3

Tx prefix hash: ead391bda8fce74c99f0e29a439d4ef42d5b374e4f33f7187d648e5341c0aaf1
Tx public key: bee80bb361ac8d77e41798136fc64d823db5ba2166cde291438ee8198fd6b57e
Timestamp: 1772227467 Timestamp [UTC]: 2026-02-27 21:24:27 Age [y:d:h:m:s]: 00:265:23:51:44
Block: 1487179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195759 RingCT/type: yes/0
Extra: 01bee80bb361ac8d77e41798136fc64d823db5ba2166cde291438ee8198fd6b57e021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 752b000240c70fda90a881a4115e8696ef139547975c900c391cb3fafdb30f6d 0.000600000000 1976643 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": 1487189, "vin": [ { "gen": { "height": 1487179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "752b000240c70fda90a881a4115e8696ef139547975c900c391cb3fafdb30f6d" } } ], "extra": [ 1, 190, 232, 11, 179, 97, 172, 141, 119, 228, 23, 152, 19, 111, 198, 77, 130, 61, 181, 186, 33, 102, 205, 226, 145, 67, 142, 232, 25, 143, 214, 181, 126, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: