Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7146c3926ffaf36a9bc591b8c669ee66b684e03ae77be5d72df33d019393fea

Tx prefix hash: 630a0d3fe5193af370943f3b437544880dc7324684904d8f320a0a6838c2fb62
Tx public key: af53fbda30a927b4a18edcbd4ef4f2a87d1d845c7bfb76e2a53b03e1c67945ee
Timestamp: 1736030020 Timestamp [UTC]: 2025-01-04 22:33:40 Age [y:d:h:m:s]: 01:321:17:04:19
Block: 1190327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493167 RingCT/type: yes/0
Extra: 01af53fbda30a927b4a18edcbd4ef4f2a87d1d845c7bfb76e2a53b03e1c67945ee021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c6f8ab1f9c4f1bd4c58467b10a60cf83353f5a1c3cb2f59ae445fff3451cccc 0.000600000000 1676842 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": 1190337, "vin": [ { "gen": { "height": 1190327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c6f8ab1f9c4f1bd4c58467b10a60cf83353f5a1c3cb2f59ae445fff3451cccc" } } ], "extra": [ 1, 175, 83, 251, 218, 48, 169, 39, 180, 161, 142, 220, 189, 78, 244, 242, 168, 125, 29, 132, 92, 123, 251, 118, 226, 165, 59, 3, 225, 198, 121, 69, 238, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: