Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b319aba9286012302d3e62ab90bbb020fa90c680405381bcccb729a37097e268

Tx prefix hash: 28d95673661b6e872d0f6d45baba1d76a96ec52a86f666b52817b03362520dc4
Tx public key: ed58a70fa76bf4bdb4ae9b046ae814e7ff411679dd8a3a55735bd34cd226c8ee
Timestamp: 1587480712 Timestamp [UTC]: 2020-04-21 14:51:52 Age [y:d:h:m:s]: 06:028:15:58:13
Block: 94636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1443439 RingCT/type: yes/0
Extra: 01ed58a70fa76bf4bdb4ae9b046ae814e7ff411679dd8a3a55735bd34cd226c8ee02110000000c4943cd9f000000000000000000

1 output(s) for total of 0.298158653596 xmr

stealth address amount amount idx tag
00: e9c4264315fc0e2e2d27ea1aa33526521d218b1be1b9ee6e379d5e89f34fc2ed 0.298158653596 168418 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": 94646, "vin": [ { "gen": { "height": 94636 } } ], "vout": [ { "amount": 298158653596, "target": { "key": "e9c4264315fc0e2e2d27ea1aa33526521d218b1be1b9ee6e379d5e89f34fc2ed" } } ], "extra": [ 1, 237, 88, 167, 15, 167, 107, 244, 189, 180, 174, 155, 4, 106, 232, 20, 231, 255, 65, 22, 121, 221, 138, 58, 85, 115, 91, 211, 76, 210, 38, 200, 238, 2, 17, 0, 0, 0, 12, 73, 67, 205, 159, 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: