Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8efbd397c53762fd8a4b381edd4d192c612e24903a53244b9e938ed4bce130

Tx prefix hash: 59ef7d1ed2098c8a037aef957139385533213bf898265cb153eac269d29cdb6b
Tx public key: 1611dd0fb8529a071bb48232c3e81fd2da73d3bd1653b2c8fb2c33ad9bf7096f
Timestamp: 1633290135 Timestamp [UTC]: 2021-10-03 19:42:15 Age [y:d:h:m:s]: 04:220:15:22:53
Block: 346013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185516 RingCT/type: yes/0
Extra: 011611dd0fb8529a071bb48232c3e81fd2da73d3bd1653b2c8fb2c33ad9bf7096f02110000000806faf294000000000000000000

1 output(s) for total of 0.043804196951 xmr

stealth address amount amount idx tag
00: 7eb958935d28e0d4e9e5683d3ebd1018e8e44ae040584bd70e547ec1e68d3744 0.043804196951 709653 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": 346023, "vin": [ { "gen": { "height": 346013 } } ], "vout": [ { "amount": 43804196951, "target": { "key": "7eb958935d28e0d4e9e5683d3ebd1018e8e44ae040584bd70e547ec1e68d3744" } } ], "extra": [ 1, 22, 17, 221, 15, 184, 82, 154, 7, 27, 180, 130, 50, 195, 232, 31, 210, 218, 115, 211, 189, 22, 83, 178, 200, 251, 44, 51, 173, 155, 247, 9, 111, 2, 17, 0, 0, 0, 8, 6, 250, 242, 148, 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: