Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f2bbb940ff258d30c86a1a353b9b94ef8ba69a482e0b549f26fde3c3952121

Tx prefix hash: 98c60a50184888f01d17893d2d4caa6db7aaa557af9a7a225d642a4368bd73f2
Tx public key: f111edb9c764bc3a5ef2d2646e2fe672f4f63cae7cfc74f0dcf1b1de3dc69bdc
Timestamp: 1583747147 Timestamp [UTC]: 2020-03-09 09:45:47 Age [y:d:h:m:s]: 06:256:04:03:14
Block: 78920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1603014 RingCT/type: yes/0
Extra: 01f111edb9c764bc3a5ef2d2646e2fe672f4f63cae7cfc74f0dcf1b1de3dc69bdc021100000001203e3db0000000000000000000

1 output(s) for total of 0.336129067202 xmr

stealth address amount amount idx tag
00: 567141596612a1d3717ae77d1184d89fc6a2cd23958b2245fb4befc5722310a4 0.336129067202 144600 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": 78930, "vin": [ { "gen": { "height": 78920 } } ], "vout": [ { "amount": 336129067202, "target": { "key": "567141596612a1d3717ae77d1184d89fc6a2cd23958b2245fb4befc5722310a4" } } ], "extra": [ 1, 241, 17, 237, 185, 199, 100, 188, 58, 94, 242, 210, 100, 110, 47, 230, 114, 244, 246, 60, 174, 124, 252, 116, 240, 220, 241, 177, 222, 61, 198, 155, 220, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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: