Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b74b6cf63cc261f7a2e3a24aa93982f49f8db5227bd1c779c60e01bf2ef6bb

Tx prefix hash: 6339e9f905673e0784b3f14aad397f486df2a650e871d9f9df23e0c1851ca096
Tx public key: 6dd1417ff4a23e7c820c73c59449df3e267bef5ae092f7104b008232753d5ae7
Timestamp: 1577611925 Timestamp [UTC]: 2019-12-29 09:32:05 Age [y:d:h:m:s]: 06:267:06:48:27
Block: 34271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1605491 RingCT/type: yes/0
Extra: 016dd1417ff4a23e7c820c73c59449df3e267bef5ae092f7104b008232753d5ae7021100000009d81c26c0000000000000000000

1 output(s) for total of 0.472548954303 xmr

stealth address amount amount idx tag
00: 32914a682add142253afa93d614c44ba81c624a28b72ae3f59eef8861216382e 0.472548954303 57644 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": 34281, "vin": [ { "gen": { "height": 34271 } } ], "vout": [ { "amount": 472548954303, "target": { "key": "32914a682add142253afa93d614c44ba81c624a28b72ae3f59eef8861216382e" } } ], "extra": [ 1, 109, 209, 65, 127, 244, 162, 62, 124, 130, 12, 115, 197, 148, 73, 223, 62, 38, 123, 239, 90, 224, 146, 247, 16, 75, 0, 130, 50, 117, 61, 90, 231, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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: