Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f9a4e6b85c572def9bd61426b0a44538393f2c08fc707c1e433e838accd17e

Tx prefix hash: 458c0c456bf6c99a00dddb9a85f1e977421946bf0f15641af298fcb9318e9e08
Tx public key: 31cb63b58b0b8623e54e9a94ca7f4613c5deae212daf6fc2e557d427e70ad1cc
Timestamp: 1574182045 Timestamp [UTC]: 2019-11-19 16:47:25 Age [y:d:h:m:s]: 06:182:14:53:13
Block: 12672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1525436 RingCT/type: yes/0
Extra: 0131cb63b58b0b8623e54e9a94ca7f4613c5deae212daf6fc2e557d427e70ad1cc021100000006ccefb800000000000000000000

1 output(s) for total of 0.557202801332 xmr

stealth address amount amount idx tag
00: e176bd47e6c713438d23962543699886d7e2145a38e9f1af9b114d550b2a17c4 0.557202801332 14266 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": 12682, "vin": [ { "gen": { "height": 12672 } } ], "vout": [ { "amount": 557202801332, "target": { "key": "e176bd47e6c713438d23962543699886d7e2145a38e9f1af9b114d550b2a17c4" } } ], "extra": [ 1, 49, 203, 99, 181, 139, 11, 134, 35, 229, 78, 154, 148, 202, 127, 70, 19, 197, 222, 174, 33, 45, 175, 111, 194, 229, 87, 212, 39, 231, 10, 209, 204, 2, 17, 0, 0, 0, 6, 204, 239, 184, 0, 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: