Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27cf6ca49ec37d23d2faac4510f94bdca40d58468308f423f4290c87e3a1b99a

Tx prefix hash: 4fdcb7a7e676c5e4a2680e9df9a9c492ebf112d40d1cb7b9b74c55a0a0c2d89e
Tx public key: 92155f3e39e71cf25a78824f6301797e6521c865bd5ac922e21af465259a99e5
Timestamp: 1627653421 Timestamp [UTC]: 2021-07-30 13:57:01 Age [y:d:h:m:s]: 05:113:06:06:14
Block: 303893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1378225 RingCT/type: yes/0
Extra: 0192155f3e39e71cf25a78824f6301797e6521c865bd5ac922e21af465259a99e5021100000028b75ebe6a000000000000000000

1 output(s) for total of 0.060405547332 xmr

stealth address amount amount idx tag
00: 37301013e07fedf33f5e83d5d5cdb0e4a1e0961abfa815c2b71e01d4c28199a0 0.060405547332 634190 of 0 -

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": 303903, "vin": [ { "gen": { "height": 303893 } } ], "vout": [ { "amount": 60405547332, "target": { "key": "37301013e07fedf33f5e83d5d5cdb0e4a1e0961abfa815c2b71e01d4c28199a0" } } ], "extra": [ 1, 146, 21, 95, 62, 57, 231, 28, 242, 90, 120, 130, 79, 99, 1, 121, 126, 101, 33, 200, 101, 189, 90, 201, 34, 226, 26, 244, 101, 37, 154, 153, 229, 2, 17, 0, 0, 0, 40, 183, 94, 190, 106, 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: