Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdb5f30327f713bf3f3f9785d3c67c21be331d860c6c550372ca31405ed96dd

Tx prefix hash: bc279d3c9fd7668b36571f8006e7ffc5f0ec373b6a7f83ae2d4bab400173aadb
Tx public key: 4e9352c248496a93f372cf38e5b8b7a0694cdb7002f0ae752152052a1b57b099
Timestamp: 1653042367 Timestamp [UTC]: 2022-05-20 10:26:07 Age [y:d:h:m:s]: 04:100:09:29:05
Block: 504957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1117415 RingCT/type: yes/0
Extra: 014e9352c248496a93f372cf38e5b8b7a0694cdb7002f0ae752152052a1b57b09902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.013027708714 xmr

stealth address amount amount idx tag
00: 22ea7586a61508ecab083ac3c9b7062a7dd3f50e9b742373a2495b855ee01f25 0.013027708714 930284 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": 504967, "vin": [ { "gen": { "height": 504957 } } ], "vout": [ { "amount": 13027708714, "target": { "key": "22ea7586a61508ecab083ac3c9b7062a7dd3f50e9b742373a2495b855ee01f25" } } ], "extra": [ 1, 78, 147, 82, 194, 72, 73, 106, 147, 243, 114, 207, 56, 229, 184, 183, 160, 105, 76, 219, 112, 2, 240, 174, 117, 33, 82, 5, 42, 27, 87, 176, 153, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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: